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. Testing performed to determine whether the system meets acceptance criteria






2. The smallest software item that can be tested in isolation.






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






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






5. Linear Code Sequence and Jump.






6. Testing an integrated system to validate it meets requirements






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






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






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






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






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






12. A functional testing approach in which test cases are designed based on business processes.






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






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






15. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






17. Response of the application to an input






18. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






21. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






29. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






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






40. A task of maintaining and controlling changes to all entities of a system.






41. One defect prevents the detection of another.






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






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






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






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






46. Human action that generates an incorrect result.






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






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






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






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