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. Requirements that determine the functionality of a software system.






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






3. Severity - Priority






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






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






6. Response of the application to an input






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






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






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






10. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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






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






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






15. Actual inputs required to execute a test case






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






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






18. Input or combination of inputs required to test software.






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






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






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






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






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






24. Testing an integrated system to validate it meets requirements






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






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






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






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






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






30. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






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






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






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






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






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






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






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






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






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. Examine changes made to an operational system cause defects.






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






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






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






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






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






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






49. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests