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. Requirements that determine the functionality of a software system.






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






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






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






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






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






7. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






10. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






12. Occurrences that happen before and after an unexpected event






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






14. A review not based on a formal documented procedure






15. Linear Code Sequence and Jump.






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






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






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






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






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






21. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






23. Human action that generates an incorrect result.






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






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






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






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






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






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






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






31. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






32. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






45. Testing software in its operational environment






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






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






48. Response of the application to an input






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






50. Conditions required to begin testing activities.