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. Sequence in which instructions are executed through a component or system






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






3. Conditions required to begin testing activities.






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






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






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






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






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






9. Severity - Priority






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






11. Component - Integration - System - Acceptance






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






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






14. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






27. Linear Code Sequence and Jump.






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






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






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






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






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






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






34. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






43. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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