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 techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






3. Response of the application to an input






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






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






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






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






8. Actual inputs required to execute a test case






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






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






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






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. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






37. Process used to create a SW product from initial conception to public release






38. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






41. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






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. Component - Integration - System - Acceptance






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






48. Testing an integrated system to validate it meets requirements






49. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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