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. One defect prevents the detection of another.






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






3. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






4. Occurrences that happen before and after an unexpected event






5. Response of the application to an input






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






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






8. Linear Code Sequence and Jump.






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






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






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






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






13. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






19. The capability of a software product to provide agreed and correct output with the required degree of precision






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






21. Tools used by developers to identify defects in programs.






22. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






23. Conditions required to begin testing activities.






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






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






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






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






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






29. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






31. Combining components or sytems into larger structural units or subsystems.






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






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






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






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






36. Waterfall iterative-incremental "V"






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






38. Human action that generates an incorrect result.






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






40. Sequence in which data items are accessed or modified by code.






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






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






43. Used to replace a component that calls another component.






44. Increased load (transations) used to test behavior of system under high volume.






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






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






47. A review not based on a formal documented procedure






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






49. Separation of testing responsibilities which encourages the accomplishment of objective testing






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