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. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






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






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






7. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






27. Record details of test cases executed Record order of execution record results






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






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






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






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






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






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






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






35. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






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






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






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






41. A review not based on a formal documented procedure






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






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






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






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






46. Occurrences that happen before and after an unexpected event






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






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






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






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