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. Based on analysis of functional specifications of a system.






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






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






4. Human action that generates an incorrect result.






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






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






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






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






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






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






11. Testing an integrated system to validate it meets requirements






12. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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






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






16. Response of the application to an input






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






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






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






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. Tools used by developers to identify defects in programs.






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






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






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






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






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






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






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






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






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






31. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






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






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






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






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






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






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






42. A review not based on a formal documented procedure






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






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






45. Sequence in which data items are accessed or modified by code.






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






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






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






49. Occurrences that happen before and after an unexpected event






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