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. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






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






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






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






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






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






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






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






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






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






13. Linear Code Sequence and Jump.






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






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






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






17. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






18. Occurrences that happen before and after an unexpected event






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






20. Behavior or response of a software application that you observe when you execute the action steps in the test case.






21. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






22. Special additions or changes to the environment required to run a test case.






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






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






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






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






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






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






29. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






32. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






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






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






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






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






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






41. Human action that generates an incorrect result.






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






43. Component - Integration - System - Acceptance






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






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






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






47. Response of the application to an input






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






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






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