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. Operational testing performed at an _external_ site without involvement of the developing organization.






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






3. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






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






5. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






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






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






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






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






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






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






15. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






18. Testing software components that are separately testable. Also module program and unit testing.






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






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






21. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






37. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






38. Testing software in its operational environment






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






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






41. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






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






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






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






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






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






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






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






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