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 unique identifier for each incident report generated during test execution.






2. Testing software in its operational environment






3. Conditions required to begin testing activities.






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






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






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






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






8. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






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






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






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






15. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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






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






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






23. Waterfall iterative-incremental "V"






24. Linear Code Sequence and Jump.






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






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






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






28. Human action that generates an incorrect result.






29. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






36. One defect prevents the detection of another.






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






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






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






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






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






42. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






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






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






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






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






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






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