QA and testing trivia

40 QA and testing trivia questions, no sign-in. Review your misses in the LoreUp app.

• Which development approach writes down what the software should do as Given–When–Then scenarios so that planners, developers, and QA can all read them?QA and testing
• Which test checks whether a product is easy to use by watching real users try to complete tasks?QA and testing
• Which test checks whether a server holds up when many people connect at once?QA and testing
• After a defect is fixed, which test runs the same steps again to check that the defect is really gone?QA and testing
• What caused the Y2K problem, also called the millennium bug?QA and testing
• What do we usually call plausible-looking fake data made up for testing?QA and testing
• When a defect that was closed as fixed shows up again, what status is it moved to?QA and testing
• What caused the software defect that lost NASA's Mars Climate Orbiter in 1999?QA and testing
• Which is the best-known unit testing framework for Java?QA and testing
• A headless browser runs without showing a window, which makes it a good fit for running browser tests on a CI server with no monitor.QA and testing
• Snapshot testing compares the current output with output saved earlier and flags whatever has changed.QA and testing
• Which test lets ordinary users try a product before its official release to find defects?QA and testing
• The later a defect is found, the more it costs to fix.QA and testing
• An app that passes its tests on one phone model can be assumed to behave the same way on other models.QA and testing
• A problem that does not get in the way of any feature, such as a typo in on-screen text, can still be reported as a defect.QA and testing
• When the same defect is reported several times, the usual practice is to keep one report and close the rest as duplicates.QA and testing
• Once testing is automated, manual testing by people is no longer needed.QA and testing
• Exploratory testing designs and runs tests on the spot while learning the product, without a scenario written in advance.QA and testing
• Static testing finds defects from the results of actually running the program.QA and testing
• Defects tend to spread evenly across all modules, so it is efficient to give every module the same amount of testing.QA and testing
• The severity and the priority of a defect are given the same value.QA and testing
• An E2E test is faster and lighter than a unit test.QA and testing
• Which test quickly runs over the core features right after a release to see that nothing is badly broken?QA and testing
• Which test checks that several modules fit together properly once they are joined?QA and testing
• Which test checks that working features have not broken after a fix?QA and testing
• What do we call the document setting out the condition to test, the steps to run, and the expected result?QA and testing
• What must always be written down alongside a defect you have found?QA and testing
• What is QA mainly responsible for?QA and testing
• Which value says how much damage a defect does to the service?QA and testing
• Which test takes one small piece, such as a function or a class, and checks it in isolation?QA and testing
• Which test walks the whole path from screen to server, the way a real user would?QA and testing
• Which way of testing checks a system through inputs and outputs alone, without looking at the internals?QA and testing
• Black box testing checks a system through its inputs and outputs alone, without looking at the internals.QA and testing
• A smoke test is the most thorough test of all, covering every feature without a gap.QA and testing
• A test case says what result should come out when you do a given thing under a given condition.QA and testing
• QA's job is not to find defects but to fix the code on the developer's behalf.QA and testing
• A bug report should carry the steps that let someone else run into the problem again.QA and testing
• A regression test checks that working features have not broken after something was fixed.QA and testing
• Test enough and you can prove that software has no defects at all.QA and testing
• A unit test takes one small piece, such as a function or a class, and checks it in isolation.QA and testing