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. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






2. A review not based on a formal documented procedure






3. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






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






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






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






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






12. Combining components or sytems into larger structural units or subsystems.






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






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






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






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






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






18. Tests interfaces between components and between integrated components and systems.






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






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






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






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






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






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






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






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






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






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






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






30. Deviation of a software system from its expected delivery services or results






31. Components are combined and tested in the order in which basic functionalities start working






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






33. Process used to create a SW product from initial conception to public release






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






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






36. Conditions required to begin testing activities.






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






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






39. Response of the application to an input






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






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






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






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






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






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






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






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






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






49. One defect prevents the detection of another.






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