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 store and manage incidents return phone defects failures or anomalies.






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






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






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






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






6. Actual inputs required to execute a test case






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






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






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






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






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






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






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






14. White-box design technique used to design test cases for a software component using LCSAJ.






15. Examine changes made to an operational system cause defects.






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






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






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






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






20. Severity - Priority






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






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






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






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






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






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






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






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






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






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






31. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






41. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






49. The capability of a software product to provide agreed and correct output with the required degree of precision






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