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. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






4. Conditions required to begin testing activities.






5. Component - Integration - System - Acceptance






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






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






8. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






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






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






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






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






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






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






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






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






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






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






21. Human action that generates an incorrect result.






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






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






24. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






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






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






39. The smallest software item that can be tested in isolation.






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






41. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






43. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






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






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






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






49. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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