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. The ratio between the number of defects found and the size of the component/system tested.






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






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






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






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






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






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






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






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






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






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






12. Ability of software to provide appropriate performance relative to amount of resources used.






13. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






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






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






17. Testing software in its operational environment






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






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






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






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






22. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






23. The smallest software item that can be tested in isolation.






24. Human action that generates an incorrect result.






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






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






27. Sequence in which instructions are executed through a component or system






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






29. Insertion of additional code in the existing program in order to count coverage items.






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






31. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






34. All possible combinations of input values and preconditions are tested.






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






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






37. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






38. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






39. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






41. Component - Integration - System - Acceptance






42. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






44. Severity - Priority






45. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






47. A set of conditions that a system needs to meet in order to be accepted by end users






48. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






49. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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