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. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






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






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






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






9. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






18. A review not based on a formal documented procedure






19. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






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






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






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






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






25. A task of maintaining and controlling changes to all entities of a system.






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






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






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






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






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






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






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






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






34. Testing software in its operational environment






35. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






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






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






40. Components are combined and tested in the order in which basic functionalities start working






41. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






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






47. Severity - Priority






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






49. Human action that generates an incorrect result.






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