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. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






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






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






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






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






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






8. Waterfall iterative-incremental "V"






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






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






11. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






20. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






21. Black-box test design technique - test cases are designed from a decision table.






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






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






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






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






26. Linear Code Sequence and Jump.






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






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






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






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






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






32. Testing an integrated system to validate it meets requirements






33. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






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






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






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






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






40. Human action that generates an incorrect result.






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






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






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






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






45. Severity - Priority






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






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






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






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






50. One defect prevents the detection of another.