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. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






4. Ability of software to provide appropriate performance relative to amount of resources used.






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






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






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






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. A unique identifier for each incident report generated during test execution.






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






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






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






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






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






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






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






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






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






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






20. Testing an integrated system to validate it meets requirements






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






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






23. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






24. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






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






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






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






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






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






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






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






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






33. Human action that generates an incorrect result.






34. Used to replace a component that calls another component.






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






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






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






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






39. One defect prevents the detection of another.






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






41. Occurrences that happen before and after an unexpected event






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






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






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






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






46. Component - Integration - System - Acceptance






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






48. Actual inputs required to execute a test case






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






50. Conditions required to begin testing activities.