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. Combining components or sytems into larger structural units or subsystems.






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






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






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






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






6. Events that occurred during the testing process our investigation.






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






8. Actual inputs required to execute a test case






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






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






11. Severity - Priority






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






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






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






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






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






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






18. Component - Integration - System - Acceptance






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






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






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






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






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






24. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






36. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






37. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






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






48. Find defects in code while the software application being tested is running.






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






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