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 technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






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






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






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






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






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






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






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






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






13. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






31. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






41. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






48. Conditions required to begin testing activities.






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






50. Used to test the functionality of software as mentioned in software requirement specifications.