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. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






4. Testing an integrated system to validate it meets requirements






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






6. Severity - Priority






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






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






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






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






11. Human action that generates an incorrect result.






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






13. Occurrences that happen before and after an unexpected event






14. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






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






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






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






20. One defect prevents the detection of another.






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






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






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






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






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






26. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






27. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






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






33. Actual inputs required to execute a test case






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






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






36. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






47. Testing software in its operational environment






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






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






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







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