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. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






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. Software products or applications designed to automate manual testing tasks.






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






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






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






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






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






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






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






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






16. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






18. Testing an integrated system to validate it meets requirements






19. One defect prevents the detection of another.






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






21. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






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






27. Testing software in its operational environment






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






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






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






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






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






33. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






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






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






41. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






44. Input or combination of inputs required to test software.






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






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






47. Waterfall iterative-incremental "V"






48. Component - Integration - System - Acceptance






49. Ability of software to provide appropriate performance relative to amount of resources used.






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