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. Black-box test design technique - test cases are designed from a decision table.






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






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






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






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






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






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






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






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






10. Linear Code Sequence and Jump.






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






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






13. Actual inputs required to execute a test case






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






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






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






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






18. Software products or applications designed to automate manual testing tasks.






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






20. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






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






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






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






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






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






27. Components are combined and tested in the order in which basic functionalities start working






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






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






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






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






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






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






34. A review not based on a formal documented procedure






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






36. Severity - Priority






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






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






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






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






41. Conditions required to begin testing activities.






42. One defect prevents the detection of another.






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






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






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






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






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






48. Deviation of a software system from its expected delivery services or results






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






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