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. Sequence in which instructions are executed through a component or system






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






3. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






7. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






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






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






13. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






14. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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






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






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






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






22. Testing software in its operational environment






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






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






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






26. Response of the application to an input






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






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






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






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






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






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






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






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






35. Waterfall iterative-incremental "V"






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






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






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






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






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






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






42. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






45. Linear Code Sequence and Jump.






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






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






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






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






50. Actual inputs required to execute a test case