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. Sequence in which instructions are executed through a component or system






2. Actual inputs required to execute a test case






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






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






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






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






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






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






9. A task of maintaining and controlling changes to all entities of a system.






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






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






12. Testing an integrated system to validate it meets requirements






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






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






15. The process of finding analyzing and removing causes of failure in a software product.






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






17. One defect prevents the detection of another.






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






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






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






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






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






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






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






25. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






35. Testing software in its operational environment






36. Component - Integration - System - Acceptance






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






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






39. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






49. Occurrences that happen before and after an unexpected event






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