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. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






24. Informal testing technique in which test planning and execution run in parallel






25. One defect prevents the detection of another.






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






27. Based on analysis of functional specifications of a system.






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






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






30. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






32. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






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






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






39. Occurrences that happen before and after an unexpected event






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






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






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






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






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






45. An event or item that can be tested using one or more test cases






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






47. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






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