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. An event or item that can be tested using one or more test cases






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






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






4. Testing software in its operational environment






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






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






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






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






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






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






11. Testing an integrated system to validate it meets requirements






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






13. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






14. Waterfall iterative-incremental "V"






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






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






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






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






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






20. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






39. Special-purpose software used to simulate a component that calls the component under test






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






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






42. Response of the application to an input






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






44. Severity - Priority






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






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






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






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






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






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