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. Integration approach components or subsystems are combined all at once rather than in stages.






2. Develop & proiroitize test cases Create groups of test cases Set up test environment






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. A review not based on a formal documented procedure






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






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






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






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. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






15. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






16. Conditions required to begin testing activities.






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






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






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






20. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






27. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






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






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






31. Testing an integrated system to validate it meets requirements






32. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






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






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






38. One defect prevents the detection of another.






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






40. Testing software in its operational environment






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






42. Component - Integration - System - Acceptance






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






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






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






46. Special additions or changes to the environment required to run a test case.






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






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






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






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