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. Components are integrated in the order in which they are developed






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






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






4. Components are combined and tested in the order in which basic functionalities start working






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






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






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






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






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






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






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






12. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






15. Occurrences that happen before and after an unexpected event






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






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






18. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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