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. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






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






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






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. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






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






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






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






15. Testing an integrated system to validate it meets requirements






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






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






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






19. Waterfall iterative-incremental "V"






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






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






22. Occurrences that happen before and after an unexpected event






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






24. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






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






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






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






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






32. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






33. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






36. Severity - Priority






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






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






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






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






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






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






43. Actual inputs required to execute a test case






44. Testing software in its operational environment






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. Testing software components that are separately testable. Also module program and unit testing.






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






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






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






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