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. Testing software components that are separately testable. Also module program and unit testing.






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






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






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






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






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






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






8. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






24. Human action that generates an incorrect result.






25. Allows storage of test input and expected results in one or more central data sources or databases.






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






27. Conditions required to begin testing activities.






28. Find defects in code while the software application being tested is running.






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






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






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






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






33. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






34. Testing software in its operational environment






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






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






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






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






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






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






41. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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