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. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






10. A review not based on a formal documented procedure






11. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






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






16. Occurrences that happen before and after an unexpected event






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






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






19. Severity - Priority






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






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






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






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






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






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






26. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






28. Human action that generates an incorrect result.






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






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






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






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






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






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






35. One defect prevents the detection of another.






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






37. Deviation of a software system from its expected delivery services or results






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






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






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






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






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






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






44. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






45. Component - Integration - System - Acceptance






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






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






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






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






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