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. Sequence in which instructions are executed through a component or system






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






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






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






5. Events that occurred during the testing process our investigation.






6. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






32. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






33. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






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






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






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






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






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






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






41. A review not based on a formal documented procedure






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






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






44. One defect prevents the detection of another.






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






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






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






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






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






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