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. Integrate different kinds of tools to make test management more efficient and simple.






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






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






4. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






20. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






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






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






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






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






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






28. Testing software in its operational environment






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






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






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






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






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






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






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






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






37. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






46. Component - Integration - System - Acceptance






47. Testing an integrated system to validate it meets requirements






48. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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