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. Used to test the functionality of software as mentioned in software requirement specifications.






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






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






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






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






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






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






8. Waterfall iterative-incremental "V"






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






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






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






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






13. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






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






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






27. Testing an integrated system to validate it meets requirements






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






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






30. Component - Integration - System - Acceptance






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






32. Linear Code Sequence and Jump.






33. Severity - Priority






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






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






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






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






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






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






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






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






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






43. Special-purpose software used to simulate a component called by the component under test






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






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






46. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






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