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. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






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






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






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






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






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






8. Special-purpose software used to simulate a component called by the component under test






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






10. Response of the application to an input






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






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






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






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






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






16. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






24. Linear Code Sequence and Jump.






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






26. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






28. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






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






32. Severity - Priority






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






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






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






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






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






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






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






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






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






42. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






47. One defect prevents the detection of another.






48. The ratio between the number of defects found and the size of the component/system tested.






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






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