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. All possible combinations of input values and preconditions are tested.






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






3. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






4. Special-purpose software used to simulate a component that calls the component under test






5. Integration approach components or subsystems are combined all at once rather than in stages.






6. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






7. One defect prevents the detection of another.






8. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






10. 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).






11. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






14. 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






15. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






16. Response of the application to an input






17. Black-box test design technique - test cases are designed from a decision table.






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






19. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






20. Based on analysis of functional specifications of a system.






21. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






23. Actual inputs required to execute a test case






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






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






26. A component of the incident report that determines the actual effect of the incident on the software and its users.






27. The ratio between the number of defects found and the size of the component/system tested.






28. The process of finding analyzing and removing causes of failure in a software product.






29. Severity - Priority






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






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






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






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






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






35. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






36. Software products or applications designed to automate manual testing tasks.






37. Testing software in its operational environment






38. A document that provides the structure for writing test cases.






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






40. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






43. Tests interfaces between components and between integrated components and systems.






44. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






45. Examine changes made to an operational system cause defects.






46. Tools used to identify and calculate coverage items in program code.






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






48. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






50. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.