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. A table showing combinations of inputs and their associated actions.






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






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






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






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






6. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






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






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






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






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






13. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






29. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






34. A review not based on a formal documented procedure






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






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






37. Testing an integrated system to validate it meets requirements






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






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






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






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






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






43. A component of the incident report that determines the actual effect of the incident on the software and its users.






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






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






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






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






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






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






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