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. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






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






8. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






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






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






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






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






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






18. Component - Integration - System - Acceptance






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






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






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






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






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






24. Human action that generates an incorrect result.






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






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






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






28. Severity - Priority






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






30. Response of the application to an input






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






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






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






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






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






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






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






38. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






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






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