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. Requirements that determine the functionality of a software system.






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






3. An analysis that determines the portion of code on software executed by a set of test cases






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






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






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






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






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






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






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






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






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






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






14. Occurrences that happen before and after an unexpected event






15. Response of the application to an input






16. Waterfall iterative-incremental "V"






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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






19. Sequence in which instructions are executed through a component or system






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






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






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






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






24. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






36. Actual inputs required to execute a test case






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






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






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






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






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






42. Conditions required to begin testing activities.






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






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






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






46. Linear Code Sequence and Jump.






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






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






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






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