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. Tools used to identify and calculate coverage items in program code.






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






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






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






5. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






13. Tools used to store and manage incidents return phone defects failures or anomalies.






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






15. One defect prevents the detection of another.






16. The process of finding analyzing and removing causes of failure in a software product.






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






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






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






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






21. Tests interfaces between components and between integrated components and systems.






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






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






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






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






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






27. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






31. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






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






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






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






37. Severity - Priority






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






39. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






50. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first