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. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






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






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






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






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






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






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






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






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






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






15. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






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






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






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






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






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






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






25. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






35. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






43. Insertion of additional code in the existing program in order to count coverage items.






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






45. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






46. One defect prevents the detection of another.






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






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






49. Component - Integration - System - Acceptance






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