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. Tools used to identify and calculate coverage items in program code.






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






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






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






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






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






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






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. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






12. Conditions required to begin testing activities.






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






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






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






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






17. Occurrences that happen before and after an unexpected event






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






19. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






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






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






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






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






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






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






29. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






47. Linear Code Sequence and Jump.






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






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






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