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. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






3. Human action that generates an incorrect result.






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






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






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






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






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






9. Response of the application to an input






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






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






12. Actual inputs required to execute a test case






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






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






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






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






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






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






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






20. Occurrences that happen before and after an unexpected event






21. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






31. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






48. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






50. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.