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. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






4. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






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






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






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






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






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






13. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






25. Testing software in its operational environment






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






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






28. A review not based on a formal documented procedure






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






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






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






32. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






34. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






37. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






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






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






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






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






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






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






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






47. Testing an integrated system to validate it meets requirements






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






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






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