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. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






5. Conditions required to begin testing activities.






6. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






15. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






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






19. Occurrences that happen before and after an unexpected event






20. Component - Integration - System - Acceptance






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






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






23. Black-box test design technique - test cases are designed from a decision table.






24. Testing software in its operational environment






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






26. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






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






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






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






32. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






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






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






38. Testing an integrated system to validate it meets requirements






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






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






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






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






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






44. Linear Code Sequence and Jump.






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






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






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






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






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






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