Data Driven Testing:
Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.
To examine the configuration, input and output sent by the base system to dependent sub-systems are as per specifications. It examines the application’s requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.
A test that exercises a feature of a product in full detail.
This is intended to break the ice to find the failure points of software through input of invalid / corrupt data, incorrect format of data, huge volume or heavy load, etc.
This is a type of Static Testing in which project documents are verified and validated for thoroughness and completeness. This testing can vary from spell check, grammar check, readability from end-user perspective, appropriateness of content, correctness of screenshots, ambiguity of meaning is checked, coverage of technical details within scope, simplicity of installation steps, EULA (End User License Agreements), User Guides, Admin Guides, Installation Guides, Porting Guides, Upgrade Guides, etc.
Testing the core or critical functionality of the software and execute them to ensure the core functionalities are working fine rather than executing all test cases. See Smoke Testing and Sanity Testing also.
Downward Compatibility Testing:
This refers to Backward Compatibility Testing.
Dry Run Testing (DRT):
This is a form of testing where the effects of a possible failure are intentionally mitigated. In computer programming, this is a mental or paper-based run of a program by scrutinizing the source code step by step to determine what it will do when run.
Testing the software through execution of the code. For eg., Unit Testing, Functional Testing, Regression Testing, System Testing, Performance Testing etc. See also Static Testing.