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. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






6. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






17. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






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






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






29. Actual inputs required to execute a test case






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






31. Occurrences that happen before and after an unexpected event






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






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






34. Testing performed to determine whether the system meets acceptance criteria






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






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. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






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






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






43. Testing an integrated system to validate it meets requirements






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






45. Response of the application to an input






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






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






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






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






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