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






2. Testing an integrated system to validate it meets requirements






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. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






8. A table showing combinations of inputs and their associated actions.






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






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






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






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






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






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






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






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






17. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






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






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






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






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






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






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






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






29. Response of the application to an input






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






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






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






33. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






41. Record details of test cases executed Record order of execution record results






42. Conditions required to begin testing activities.






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






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






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






46. Software products or applications designed to automate manual testing tasks.






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






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






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






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