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






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






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






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






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






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






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






8. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






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






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






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






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






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






14. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






25. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






26. One defect prevents the detection of another.






27. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






32. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






33. A review not based on a formal documented procedure






34. Deviation of a software system from its expected delivery services or results






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






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






37. Testing software in its operational environment






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






39. Human action that generates an incorrect result.






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






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






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






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






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






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






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






47. Component - Integration - System - Acceptance






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






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






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