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. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






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






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






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






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






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






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






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






12. Examine changes made to an operational system cause defects.






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






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






15. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






16. One defect prevents the detection of another.






17. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






27. Testing software in its operational environment






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






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






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






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






32. Linear Code Sequence and Jump.






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






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






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






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






37. Record details of test cases executed Record order of execution record results






38. Waterfall iterative-incremental "V"






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






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






41. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






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






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






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






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






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