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. The process of finding analyzing and removing causes of failure in a software product.






2. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






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






13. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






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






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






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






19. Occurrences that happen before and after an unexpected event






20. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






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






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






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






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






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






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






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. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






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






37. Human action that generates an incorrect result.






38. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






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






43. Waterfall iterative-incremental "V"






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






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






46. Severity - Priority






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






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






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






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