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






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






3. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






11. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






20. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






31. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






33. Events that occurred during the testing process our investigation.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






48. Tools used by developers to identify defects in programs.






49. Conditions required to begin testing activities.






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