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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






7. Testing software in its operational environment






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






9. Requirements that determine the functionality of a software system.






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






11. Special-purpose software used to simulate a component that calls the component under test






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






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






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






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






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






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






18. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






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






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






24. Testing an integrated system to validate it meets requirements






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






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






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






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






29. A review not based on a formal documented procedure






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






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






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






33. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






47. One defect prevents the detection of another.






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






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






50. Conditions required to begin testing activities.