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. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






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






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






10. Testing software in its operational environment






11. Examine changes made to an operational system cause defects.






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






13. Linear Code Sequence and Jump.






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






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






16. Conditions required to begin testing activities.






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






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






19. Occurrences that happen before and after an unexpected event






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






21. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






22. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






23. Actual inputs required to execute a test case






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






25. Response of the application to an input






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






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






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






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






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






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






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






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






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






35. Software products or applications designed to automate manual testing tasks.






36. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






37. Component - Integration - System - Acceptance






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






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






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






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






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






43. Increased load (transations) used to test behavior of system under high volume.






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






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






46. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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






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






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