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. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






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






3. Occurrences that happen before and after an unexpected event






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






5. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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






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






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






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






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. Process used to create a SW product from initial conception to public release






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






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






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






16. The ratio between the number of defects found and the size of the component/system tested.






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






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






19. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






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






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






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






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






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






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






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






31. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






34. Component - Integration - System - Acceptance






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






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






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






38. Insertion of additional code in the existing program in order to count coverage items.






39. Components are integrated in the order in which they are developed






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






41. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






43. A functional testing approach in which test cases are designed based on business processes.






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






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






46. Actual inputs required to execute a test case






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






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






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






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