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 document that records the description of each event that occurs during the testing process and that requires further investigation






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






3. Component - Integration - System - Acceptance






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






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






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






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






8. Special-purpose software used to simulate a component that calls the component under test






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






10. Severity - Priority






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






12. A document that provides the structure for writing test cases.






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






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






15. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






36. Human action that generates an incorrect result.






37. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






47. A review not based on a formal documented procedure






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






49. Conditions required to begin testing activities.






50. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.