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. Examine changes made to an operational system cause defects.






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






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






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






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






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






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






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






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






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






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






12. A table showing combinations of inputs and their associated actions.






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






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






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






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






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






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






19. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






37. Response of the application to an input






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






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






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






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






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






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






44. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






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






48. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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