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. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






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






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






7. Black-box test design technique - test cases are designed from a decision table.






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






9. Testing software in its operational environment






10. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






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






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






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






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






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






17. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






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






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






21. Testing an integrated system to validate it meets requirements






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






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






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






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






26. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






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






37. A review not based on a formal documented procedure






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






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






40. Human action that generates an incorrect result.






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






42. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






43. Actual inputs required to execute a test case






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






45. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






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