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. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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






4. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






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






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






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






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






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






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






16. Special-purpose software used to simulate a component that calls the component under test






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






18. Sequence in which data items are accessed or modified by code.






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






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






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






22. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






25. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






26. Human action that generates an incorrect result.






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






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






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






30. Conditions required to begin testing activities.






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






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






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






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






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






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






37. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






48. Occurrences that happen before and after an unexpected event






49. Actual inputs required to execute a test case






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