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. Sequence in which instructions are executed through a component or system






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






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






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






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






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






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






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






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






10. The process of finding analyzing and removing causes of failure in a software product.






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






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






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. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






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






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






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






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






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






25. Linear Code Sequence and Jump.






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






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






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






29. A unique identifier for each incident report generated during test execution.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






45. The ratio between the number of defects found and the size of the component/system tested.






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






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






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






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






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