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 technique used to improve testing coverage by deliberately introducing faults in code.






2. Software products or applications designed to automate manual testing tasks.






3. Component - Integration - System - Acceptance






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






5. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






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






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






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






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






12. Response of the application to an input






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






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






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






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






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






18. Testing software in its operational environment






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






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






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






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






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






24. Occurrences that happen before and after an unexpected event






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






26. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






31. Conditions required to begin testing activities.






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






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






34. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






35. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






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






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






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






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






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






46. Human action that generates an incorrect result.






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






48. One defect prevents the detection of another.






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






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