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. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






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






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






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






8. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






15. Actual inputs required to execute a test case






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






17. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






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






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






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






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






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






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






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






27. Waterfall iterative-incremental "V"






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






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






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






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






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






33. Severity - Priority






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






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






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






37. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






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






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






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






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






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






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






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






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