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






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






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






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






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






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






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






8. Occurrences that happen before and after an unexpected event






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






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






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






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






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






14. Human action that generates an incorrect result.






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






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






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






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






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






20. Conditions required to begin testing activities.






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






22. One defect prevents the detection of another.






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






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






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






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






27. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






34. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






37. Testing software in its operational environment






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






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






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






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. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






44. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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