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. An event or item that can be tested using one or more test cases






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






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






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






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






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






7. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






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






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






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






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






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






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






16. Occurrences that happen before and after an unexpected event






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






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






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






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






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






22. Measures amount of testing performed by a collection of test cases






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






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






25. Actual inputs required to execute a test case






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






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






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






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






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






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






32. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






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






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






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






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






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






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






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






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






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






47. Response of the application to an input






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






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






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