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. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






3. Conditions required to begin testing activities.






4. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






6. All possible combinations of input values and preconditions are tested.






7. Actual inputs required to execute a test case






8. The smallest software item that can be tested in isolation.






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






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






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






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






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






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






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






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






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






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






19. One defect prevents the detection of another.






20. Occurrences that happen before and after an unexpected event






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






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






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






24. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.






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






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






27. Testing an integrated system to validate it meets requirements






28. Component - Integration - System - Acceptance






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






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






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






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






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






34. Components are integrated in the order in which they are developed






35. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






49. Informal testing technique in which test planning and execution run in parallel






50. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports