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. Tools used to identify and calculate coverage items in program code.






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






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






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






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






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






8. Occurrences that happen before and after an unexpected event






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






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






11. Conditions required to begin testing activities.






12. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






23. Actual inputs required to execute a test case






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






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






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






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






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






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






30. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






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






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






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






37. Black-box test design technique - test cases are designed from a decision table.






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






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






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






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






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






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






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






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






46. An analysis that determines the portion of code on software executed by a set of test cases






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






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






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






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