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. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






20. Response of the application to an input






21. Actual inputs required to execute a test case






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






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






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






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






26. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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