Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Sequence in which data items are accessed or modified by code.






2. Component - Integration - System - Acceptance






3. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






4. Human action that generates an incorrect result.






5. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






6. Waterfall iterative-incremental "V"






7. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






8. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






9. Black-box testing technique used to create groups of input conditions that create the same kind of output.






10. Components are integrated in the order in which they are developed






11. Requirements that determine the functionality of a software system.






12. A review not based on a formal documented procedure






13. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






14. A table showing combinations of inputs and their associated actions.






15. Process used to create a SW product from initial conception to public release






16. Allows storage of test input and expected results in one or more central data sources or databases.






17. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






18. An analysis that determines the portion of code on software executed by a set of test cases






19. Actual inputs required to execute a test case






20. Measures amount of testing performed by a collection of test cases






21. Tools used to store and manage incidents return phone defects failures or anomalies.






22. One defect prevents the detection of another.






23. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






24. Used to test the functionality of software as mentioned in software requirement specifications.






25. Record details of test cases executed Record order of execution record results






26. Input or combination of inputs required to test software.






27. Testing performed to determine whether the system meets acceptance criteria






28. A unique identifier for each incident report generated during test execution.






29. Occurrences that happen before and after an unexpected event






30. Incident Report - Identifier - Summary - Incident - Description - Impact






31. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






32. Integrate different kinds of tools to make test management more efficient and simple.






33. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






34. Find defects in code while the software application being tested is running.






35. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






36. An event or item that can be tested using one or more test cases






37. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






38. Deviation of a software system from its expected delivery services or results






39. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






40. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






41. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






42. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






43. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






44. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






45. A task of maintaining and controlling changes to all entities of a system.






46. A functional testing approach in which test cases are designed based on business processes.






47. Informal testing technique in which test planning and execution run in parallel






48. Testing software in its operational environment






49. Special-purpose software used to simulate a component called by the component under test






50. Components are combined and tested in the order in which basic functionalities start working