Atlassian Software Testing Interview Questions & Answers

Re-testing existing features after a change. Automate stable, repetitive, high-value flows that run every release.

The extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.

Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.

Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.

Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.

Unit, integration, system and acceptance testing, moving from individual components to the complete product in front of users.

Black box tests behaviour without code knowledge; white box tests internal logic and paths; grey box uses partial knowledge of the internals.

Break the work into modules and test cases, use past velocity or three-point estimation (optimistic, likely, pessimistic), add time for test data, environment issues, retesting and regression, and keep a risk buffer.

Positive cases use valid inputs to confirm expected behaviour; negative cases use invalid inputs to confirm the system handles errors gracefully.

A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.

A model with many fast unit tests at the base, fewer API or integration tests in the middle and a small number of UI tests at the top.

TDD writes unit tests before code to drive design; BDD describes behaviour in business language scenarios that become automated acceptance tests.

Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.

Sprint planning (estimate test effort), daily stand-up (status and blockers), sprint review (demo) and retrospective (improve). Testers clarify acceptance criteria early and test within the sprint.

Severity = impact on the system. Priority = urgency to fix. Logo misspelt on the homepage → low severity, high priority. Crash in a rarely used report → high severity, low priority.

Valid card and PIN, wrong PIN, three failed attempts, amount above balance, amount above daily limit, invalid denomination, machine out of cash, network failure and receipt printing.

List conditions and actions in a table and cover every combination of conditions (rules) — ideal for business rules like loan approval: salary > X AND credit score > Y → approve.

Smoke testing checks that the critical features of a new build work (broad and shallow). Sanity testing checks that a specific fix or area works after a change (narrow and deep).

Check SQL injection, brute-force lockout, password masking, session timeout, HTTPS, cookie flags, error messages not revealing users and password reset flow.

Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.

Valid login, invalid login, forgot password, locked account and session handling are the main scenarios to cover.

Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.

Verifying the application works across different hardware, software and settings combinations.

Functional testing checks what the system does (login, checkout). Non-functional testing checks how well it does it (performance, security, usability, compatibility).

Test 17, 18, 19, 59, 60 and 61.

User Acceptance Testing — end users or the client verify that the system meets business needs in a production-like environment before go-live.

Finding why a defect was introduced, such as unclear requirements or missed reviews, to prevent similar defects in future.

State the problem, location and condition briefly, for example 'Checkout button disabled after applying a coupon on the cart page'.

They let testers verify totals and counts per category, such as the number of orders per customer, and compare them with the UI or reports.

Assess impact and risk, discuss with product and dev, decide to fix, defer with a workaround or delay release, and document the decision.

Valid keyword, partial match, no results, special characters, very long text, empty search, case sensitivity, spelling errors, suggestions and speed of results.

A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.

The number of defects per size of software, for example defects per thousand lines of code or per module, used to compare quality.

Statuses like To Do, In Progress, In Review, Ready for QA, Done and Reopened, with transitions that depend on the team's configuration.

Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.

Test execution rate, pass percentage, defect density, defect leakage, defect rejection ratio, requirement coverage and automation coverage.

Testing services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.

A scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.

Internationalisation tests that the product can support many languages and formats; localisation tests that a specific locale is correct for text, currency, date and layout.

Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.

An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are defects.

A language to query databases. Testers use it to verify data saved by the application, prepare test data and check backend results.

SDLC is the full software development life cycle; STLC is the testing life cycle: requirement analysis, test planning, test design, environment setup, execution and closure.

A final document summarising what was tested, defects found and open, metrics, lessons learned and the recommendation for release.

Learning, test design and execution at the same time, without scripted cases — time-boxed sessions with a charter (e.g. 'explore checkout with coupons'), noting bugs and ideas. Great for finding edge cases.

Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.

A suite is a collection of related test cases; a run is one execution of a set of tests against a build.

Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.

Check access with valid, expired and missing tokens, role-based permissions, error codes and that sensitive data is never exposed.