Featured

    Featured Posts

Difference b/w verification Vs validation and executable and non-executable testing


Difference between validation and verification, verification vs validation, difference between executable and non-executable testing, executable vs non-executable testing, execution based testing vs execution based testing.

(a) Difference between verification and validation :

Verification
Validation
Verification ensures that the product is designed to deliver all functionality to the customer
Validation ensures that functionality is the intended behavior of the product.
It involves reviews and meetings to evaluate documents, plans, code, requirements and specifications.
It involves actual testing and takes place after verification is completed
It evaluates documents, plans, code, requirements and specifications.
It evaluates the product itself.
Inputs are checklists, issues lists, inspection meetings, reviews and meetings.
It is the actual testing of the actual product.
Output is a nearly perfect set of documents, plans specifications and requirements document.
Output is a nearly perfect product.


Difference between validation and verification, verification vs validation, difference between executable and non-executable testing, executable vs non-executable testing, execution based testing vs execution based testing.

(b) Executable and Non-executable :

(i)  Execution based testing : In this type of testing, the modules are run against test cases.  Following are the two ways of systematically constructing test data to test a module :
  1. Black-Box testing :  The code itself is ignored, the only information used in designing test cases is the specification document.
  2. White-Box Testing :  The code itself is tested, without regard of the specifications.
(ii)  Non-execution based testing :  The non-execution based testing relies on fault detection strategy.  The fault-detecting power of these non-execution based techniques leads to rapid, through, and early fault detection. The additional time required for code reviews is more that repaid by the increased productivity due to fewer faults at the integration phase.
       In general, non-execution based code testing is less expensive than execution-based testing because :
  1. Execution-based testing (running test case) can be extremely time-consuming, and 
  2. Reviews lead to detection of faults earlier in the life cycle.
Non-execution based testing is also known as static testing (or static program analysis).

 

Post a Comment

www.CodeNirvana.in

www.posthatke.com. Powered by Blogger.

Google+ Followers

Copyright © www.posthatke.com | Blogger Templates | Designed By posthatke.com