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. Testing software in its operational environment






2. Occurrences that happen before and after an unexpected event






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






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






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






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






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






8. A set of conditions that a system needs to meet in order to be accepted by end users






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






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






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






12. A technique used to improve testing coverage by deliberately introducing faults in code.






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






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






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






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






17. A functional testing approach in which test cases are designed based on business processes.






18. Severity - Priority






19. A review not based on a formal documented procedure






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






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






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






23. Deviation of a software system from its expected delivery services or results






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






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






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






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






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






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






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






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






32. Actual inputs required to execute a test case






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






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






35. Component - Integration - System - Acceptance






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






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






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






39. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






45. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






46. Conditions required to begin testing activities.






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






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






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






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