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. One defect prevents the detection of another.






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






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






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






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






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






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






8. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






10. Waterfall iterative-incremental "V"






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






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






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






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






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






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






17. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






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






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






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






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






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






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






32. Find defects in code while the software application being tested is running.






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






34. Response of the application to an input






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






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






37. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






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. Special additions or changes to the environment required to run a test case.






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






43. Actual inputs required to execute a test case






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






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






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






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






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






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






50. Insertion of additional code in the existing program in order to count coverage items.