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. The process of finding analyzing and removing causes of failure in a software product.






2. A table showing combinations of inputs and their associated actions.






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






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






5. Linear Code Sequence and Jump.






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






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






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






9. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






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






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






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






18. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






21. Occurrences that happen before and after an unexpected event






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






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






24. Special-purpose software used to simulate a component that calls the component under test






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






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






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






28. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






29. Waterfall iterative-incremental "V"






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






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






32. Testing software in its operational environment






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






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






35. A functional testing approach in which test cases are designed based on business processes.






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






37. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






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






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






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






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






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






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






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






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






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






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