QA Engineer
Testing fundamentals and strategy questions
187 questions on Testing fundamentals and strategy for qa engineers, easiest first.
Easy 73
- Smoke testingeasy
- Severity vs priorityeasy
- What makes a good bug reporteasy
- Verification vs validationeasy
- Purpose of regression testingeasy
- STLC phase ordereasy
- Integration testing leveleasy
- Sanity testingeasy
- Bug fails retesteasy
- Entry criteria for testingeasy
- Static testing exampleeasy
- Spotting a non-functional requirementeasy
- Alpha vs beta testingeasy
- Who does UATeasy
- Probing for SQL injectioneasy
- Testing a search box for XSSeasy
- Traceability matrixeasy
- Test plan vs test strategyeasy
- Finding the failing API calleasy
- The pesticide paradoxeasy
- Mobile interruption testingeasy
- What a spike test checkseasy
- Why run a baseline testeasy
- Finding the maximum capacityeasy
- Running a smoke test firsteasy
- What a volume test checkseasy
- What a scalability test checkseasy
- A testable performance requirementeasy
- Why include a warm-upeasy
- Performance checks in CIeasy
- Which journeys to script firsteasy
- Ready to start the load test?easy
- Synthetic monitoring or load testeasy
- SLA, SLO and SLIeasy
- A useful load test reporteasy
- Error, defect and failureeasy
- Why not test everythingeasy
- Testing earlyeasy
- Defect clusteringeasy
- Bug-free but uselesseasy
- What testing can proveeasy
- QA or QCeasy
- Stub or drivereasy
- What a unit test checkseasy
- Testing the whole systemeasy
- Confirmation testingeasy
- Load or stress testeasy
- Running a load for hourseasy
- Usability testingeasy
- i18n or l10neasy
- Basis of white-box testingeasy
- Monkey testingeasy
- Operational acceptance testingeasy
- Installation testingeasy
- Images and screen readerseasy
- Using the site without a mouseeasy
- Writing a bug titleeasy
- Two bugs in one reporteasy
- Reporting an intermittent bugeasy
- What a test environment includeseasy
- Test summary reporteasy
- Stating what is out of scopeeasy
- A new phone OS versioneasy
- Rotating the phone mid-formeasy
- User says no to locationeasy
- Maintenance testingeasy
- Impact analysiseasy
- Who leads a walkthrougheasy
- The test basiseasy
- Test conditioneasy
- A test harnesseasy
- Gorilla testingeasy
- Tests that cannot runeasy
Medium 63
- The test pyramidmedium
- Developer cannot reproducemedium
- Only one day to testmedium
- Calculating DREmedium
- File upload validationmedium
- Search that misses accentsmedium
- Real RTL bug in Arabic UImedium
- Using production data for testsmedium
- Forcing a backend errormedium
- Choosing devices to testmedium
- Three Amigos sessionmedium
- Reporting the steady-state windowmedium
- Prioritising by risk scoremedium
- Top-down or bottom-upmedium
- Big-bang integrationmedium
- Pairs in the V-modelmedium
- The most formal reviewmedium
- What static analysis findsmedium
- Grey-box testingmedium
- A sudden rushmedium
- Scalability or volumemedium
- Killing the main databasemedium
- Choosing browsers to testmedium
- Agile testing quadrant 4medium
- Testing in the Definition of Donemedium
- Canary releasemedium
- Three-point test estimatemedium
- Defect densitymedium
- Execution and pass ratesmedium
- Reopened statusmedium
- Deferred defectsmedium
- Bug that is not a bugmedium
- A good exit criterionmedium
- Building a device matrixmedium
- Testing on a budget phonemedium
- Testing on a slow networkmedium
- Connection lost after payingmedium
- Upgrading from an old versionmedium
- A deep link with no appmedium
- The Android back gesturemedium
- Using a cloud device farmmedium
- Testing dark modemedium
- Bigger system fontmedium
- Measuring app start timemedium
- Sync delayed overnightmedium
- Translated labels that do not fitmedium
- Hindi text shown wronglymedium
- The triage meetingmedium
- Measuring defect agemedium
- A reactive strategymedium
- Reviewing a requirementmedium
- When to start testing a storymedium
- Configuration testingmedium
- One bug hiding anothermedium
- Making a system testablemedium
- A quality gate in CImedium
- Staging not like productionmedium
- A bug only on Safarimedium
- Native, hybrid or mobile webmedium
- Requirement changed mid-sprintmedium
- Limits of accessibility scannersmedium
- Testing one microservicemedium
- Handling beta feedbackmedium
Hard 51
- Viewing another user's invoicehard
- 100% code coveragehard
- Go or no-gohard
- Tampering with a JWThard
- Mass assignment in profile updatehard
- XSS that survives HTML encodinghard
- Arabic digits rejectedhard
- Mutation scorehard
- Contract green, production brokenhard
- App killed in the backgroundhard
- Is 10% slower a real regression?hard
- Load testing the live sitehard
- A name that runs in Excelhard
- Upload cut off halfwayhard
- In-flight requests by Little's Lawhard
- Downtime allowed by 99.9%hard
- Reading the 95th percentilehard
- Calculating an Apdex scorehard
- Product or project riskhard
- A regression-averse strategyhard
- Downside of full independencehard
- Testing an urgent hotfixhard
- Testing a data migrationhard
- Proving backups can be restoredhard
- Running a chaos experimenthard
- Load test on a small environmenthard
- Text contrast that failshard
- Many bugs rejectedhard
- Rare bug, serious damagehard
- Deleting a user's datahard
- Pre-ticked consent boxhard
- Token still works after logouthard
- Is it slower than beforehard
- When a partner service is downhard
- Full requirement coverage, still badhard
- When automation pays offhard
- App Not Responding on Androidhard
- Changing the phone datehard
- Testing on a rooted phonehard
- An icon button with no namehard
- Using crowd testershard
- When to stop a canaryhard
- Memory that keeps climbinghard
- Throughput stops growinghard
- Analysing an escaped bughard
- Testing a model's predictionshard
- A dark launchhard
- Proof of testing for audithard
- Where a bug should be caughthard
- Synthetic checks in productionhard
- A bug during a change freezehard