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. Special-purpose software used to simulate a component that calls the component under test






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






3. Response of the application to an input






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






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






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






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






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






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






10. Linear Code Sequence and Jump.






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






12. Tools used to store and manage incidents return phone defects failures or anomalies.






13. One defect prevents the detection of another.






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






15. Occurrences that happen before and after an unexpected event






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






17. Input or combination of inputs required to test software.






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






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






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






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






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






23. Severity - Priority






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






25. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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






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






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






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






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






32. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






49. Human action that generates an incorrect result.






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