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






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






3. Severity - Priority






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






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






6. A review not based on a formal documented procedure






7. Tools used by developers to identify defects in programs.






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






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






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






11. Waterfall iterative-incremental "V"






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






13. Record details of test cases executed Record order of execution record results






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






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






16. Testing an integrated system to validate it meets requirements






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






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






19. Sequence in which data items are accessed or modified by code.






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






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






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






23. Testing software in its operational environment






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






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






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






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






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






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






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






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






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. Informal testing technique in which test planning and execution run in parallel






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






35. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






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






45. Occurrences that happen before and after an unexpected event






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






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






48. Conditions required to begin testing activities.






49. One defect prevents the detection of another.






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