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. Human action that generates an incorrect result.






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






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






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






5. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






6. A review not based on a formal documented procedure






7. An event or item that can be tested using one or more test cases






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






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






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






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






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






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






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






15. Testing performed to determine whether the system meets acceptance criteria






16. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






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






21. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






22. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






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






37. Combining components or sytems into larger structural units or subsystems.






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






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






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






41. Testing an integrated system to validate it meets requirements






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






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






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






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






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






47. Actual inputs required to execute a test case






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






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






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