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. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






32. A component of the incident report that determines the actual effect of the incident on the software and its users.






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






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






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






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






37. Conditions required to begin testing activities.






38. All possible combinations of input values and preconditions are tested.






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






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






41. Testing software in its operational environment






42. A set of conditions that a system needs to meet in order to be accepted by end users






43. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






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






49. A review not based on a formal documented procedure






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







Sorry!:) No result found.

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