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. Input or combination of inputs required to test software.






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






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






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






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






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






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






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






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






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






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






12. Testing software in its operational environment






13. Ability of software to provide appropriate performance relative to amount of resources used.






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






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






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






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






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






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






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






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






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






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






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






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






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






27. Conditions required to begin testing activities.






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






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






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






31. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






33. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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






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






37. Linear Code Sequence and Jump.






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






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






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






42. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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