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. A unique identifier for each incident report generated during test execution.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






18. Severity - Priority






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






20. Testing software in its operational environment






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






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






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






24. Testing software components that are separately testable. Also module program and unit testing.






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






26. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






29. A review not based on a formal documented procedure






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






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






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






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






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






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






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






37. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






48. Linear Code Sequence and Jump.






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






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