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 additions or changes to the environment required to run a test case.






2. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






3. Testing software in its operational environment






4. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






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






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






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






9. Linear Code Sequence and Jump.






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






11. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






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






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






18. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






22. Waterfall iterative-incremental "V"






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






24. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






27. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






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






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






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






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






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






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






36. Component - Integration - System - Acceptance






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






38. Testing an integrated system to validate it meets requirements






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






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






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






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






43. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






44. Deviation of a software system from its expected delivery services or results






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






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






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






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






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






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