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. Informal testing technique in which test planning and execution run in parallel






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






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






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






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






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






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






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






9. Occurrences that happen before and after an unexpected event






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






11. A functional testing approach in which test cases are designed based on business processes.






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






13. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






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






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






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






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






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






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






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






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






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






24. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






40. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






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






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






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






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






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






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