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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






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






9. Severity - Priority






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






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






12. Testing an integrated system to validate it meets requirements






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






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






15. Tools used to store and manage incidents return phone defects failures or anomalies.






16. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






30. Occurrences that happen before and after an unexpected event






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






32. Waterfall iterative-incremental "V"






33. A task of maintaining and controlling changes to all entities of a system.






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






35. Measures amount of testing performed by a collection of test cases






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






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






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






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






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






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






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






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






44. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






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. The smallest software item that can be tested in isolation.






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






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






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