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. A set of conditions that a system needs to meet in order to be accepted by end users






2. An event or item that can be tested using one or more test cases






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






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






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






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






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






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






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






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






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






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






13. Used to replace a component that calls another component.






14. A review not based on a formal documented procedure






15. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






24. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






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






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






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






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






31. Response of the application to an input






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






33. Waterfall iterative-incremental "V"






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






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






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. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






41. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






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






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






46. The smallest software item that can be tested in isolation.






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






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






49. Testing software in its operational environment






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