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. Allows storage of test input and expected results in one or more central data sources or databases.






2. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






11. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






27. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






40. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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






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






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






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






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






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






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






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






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