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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






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






8. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






18. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






29. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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