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 provide support for and automation of managing various testing documents such as test policy test strategy and test plan






2. Process used to create a SW product from initial conception to public release






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






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






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






6. Conditions required to begin testing activities.






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






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






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






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






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






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






13. Severity - Priority






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






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






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






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






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






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






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






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






22. Allows storage of test input and expected results in one or more central data sources or databases.






23. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






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






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






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






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






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






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






35. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






36. Waterfall iterative-incremental "V"






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






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






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






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






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






42. Occurrences that happen before and after an unexpected event






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






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






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






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






47. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






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






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






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