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 test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






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






5. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






8. Waterfall iterative-incremental "V"






9. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






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






19. One defect prevents the detection of another.






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






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






22. Testing an integrated system to validate it meets requirements






23. Record details of test cases executed Record order of execution record results






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






45. Severity - Priority






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






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






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






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






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