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. Based on analysis of functional specifications of a system.






2. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






21. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






22. Used to replace a component that calls another component.






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






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






25. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






33. A review not based on a formal documented procedure






34. Conditions required to begin testing activities.






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






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






37. Actual inputs required to execute a test case






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






39. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






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






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






42. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






43. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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