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. Tools used to identify and calculate coverage items in program code.






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






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






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






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






6. Linear Code Sequence and Jump.






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






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






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






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






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






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






13. Conditions required to begin testing activities.






14. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






30. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






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






32. A task of maintaining and controlling changes to all entities of a system.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






48. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






50. An event or item that can be tested using one or more test cases