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. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






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






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






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






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






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






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






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






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






11. The ratio between the number of defects found and the size of the component/system tested.






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






13. Severity - Priority






14. Occurrences that happen before and after an unexpected event






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






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






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






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






19. Waterfall iterative-incremental "V"






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






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






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






23. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






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






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






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






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






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






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






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






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






35. Actual inputs required to execute a test case






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






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






38. All possible combinations of input values and preconditions are tested.






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






40. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






41. Deviation of a software system from its expected delivery services or results






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






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






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






45. Component - Integration - System - Acceptance






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






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






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






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






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







Sorry!:) No result found.

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