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. Occurrences that happen before and after an unexpected event






2. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






12. Testing software in its operational environment






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






14. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






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






24. Human action that generates an incorrect result.






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






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






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






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






29. One defect prevents the detection of another.






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






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






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






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






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






35. Conditions required to begin testing activities.






36. Testing an integrated system to validate it meets requirements






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






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






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






40. A set of conditions that a system needs to meet in order to be accepted by end users






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






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






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






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






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






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






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






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






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






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