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. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






3. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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






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






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






8. Testing software in its operational environment






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






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






11. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






36. A review not based on a formal documented procedure






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






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






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






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






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






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






43. Severity - Priority






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






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






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






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






48. An analysis that determines the portion of code on software executed by a set of test cases






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






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests