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. Integrate different kinds of tools to make test management more efficient and simple.






2. Actual inputs required to execute a test case






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






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






5. Sequence in which instructions are executed through a component or system






6. Testing an integrated system to validate it meets requirements






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






8. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






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






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






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






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






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






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






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






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






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






21. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






22. Testing software in its operational environment






23. One defect prevents the detection of another.






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






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






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






27. A review not based on a formal documented procedure






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






29. Combining components or sytems into larger structural units or subsystems.






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






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






32. Component - Integration - System - Acceptance






33. Human action that generates an incorrect result.






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






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






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






37. Occurrences that happen before and after an unexpected event






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






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






40. Severity - Priority






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






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






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






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






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






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






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






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






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






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