User Tools

Site Tools


codesnippets:verificationandvalidation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
codesnippets:verificationandvalidation [2022/10/11 09:02] – created f2b216codesnippets:verificationandvalidation [2025/10/08 00:48] (current) – external edit 127.0.0.1
Line 5: Line 5:
 ===== Test Rules ===== ===== Test Rules =====
  
-  * All tests are automated by using the bash file "st"+  * All tests are created according to the [[codesnippets:testingconventions|Testing conventions]] 
-    * The test results are written into file "TestResult.txt" in folder "test".+  * All tests are automated by using the bash file 'test.bat', 'test.sh' or 'test.zsh'
 +    * The test results are written into file "result.txt" in folder "test".
   * Checks are conducted before dry runs of test:   * Checks are conducted before dry runs of test:
 +    * All library files have a corresponding test files ("Spec _ _ _ .hs")
 +      * e.g. functions in file "./src/Code.hs" have tests in "./test/SpecCode.hs"
 +    * All test files are newer than their corresponding library files
     * All functions, classes, laws of classes (if applicable) are defined by code comments     * All functions, classes, laws of classes (if applicable) are defined by code comments
-    * All functions have test tests in corresponding file "Spec___.hs+    * All tests are complete and documented according to the [[codesnippets:testingconventions|Testing conventions]] 
-      e.g. functions in file "./src/CharCode.hshave tests in "./test/SpecCharCode.hs+    * The file "package.yamlis configured to compile the final product with optimisation flag "-O2". 
-    * All tests are complete +    The content of "ChangeLog.md" 
-      * test all functions at edge cases, and boundaries +      * status up-to-date 
-      * test all function properties (probabilistically+    * The version number in file "ChangeLog.mdand "package.yaml" is consistent. 
-      test all characteristics at edge cases, and boundaries +    * The file "stack.yaml" is configured to used the latest recommended resolver. 
-      * test all characteristics as properties (probabilistically+    * The content of "README.md" is still valid 
-  * Checks are conducted after test:+      * explains how to obtaininstall and use the software 
 +      * has (an) up-to-date copyright year(s
 +    The content of file "LICENSE" is correct 
 +      * has (anup-to-date copyright year(s) 
 +      * contact information still correct? 
 +  * Conduct automated tests 
 +  * Checks are conducted after automated test:
     * File "testresult.txt" in folder "test" is newer than all products and by-products, at least including:     * File "testresult.txt" in folder "test" is newer than all products and by-products, at least including:
       * executables       * executables
       * libraries       * libraries
       * documentation       * documentation
-    * All functions are in libraries that have a corresponding file "Spec___.hs" +    * All binaries are rebuild completely (check modification dates) 
-      * e.g. for the file "./src/CharCode.hs" is also a file "./test/SpecCharCode.hs"+    * All library files have a corresponding test files ("Spec _ _ _ .hs") 
 +      * e.g. for the file "./src/Code.hs" is also a file "./test/SpecCode.hs"
     * All spec modules are imported and used in file "./test/Spec.hs", by      * All spec modules are imported and used in file "./test/Spec.hs", by 
       * review of Spec.hs-files ("./test/Spec.hs", "./test/ModuleSpec.hs")       * review of Spec.hs-files ("./test/Spec.hs", "./test/ModuleSpec.hs")
Line 28: Line 39:
         * criteria:         * criteria:
           * tests for all classes, it's laws and it's functions that are validated according to Spec.hs-files are also executed           * tests for all classes, it's laws and it's functions that are validated according to Spec.hs-files are also executed
-    * All functions are in all module "Spec___.hs"+    * All functions are in all module "Spec _ _ _ .hs"
       * e.g. for the file "./src/CharCode.hs" is also a file "./test/SpecCharCode.hs"       * e.g. for the file "./src/CharCode.hs" is also a file "./test/SpecCharCode.hs"
 +    * All functions described and hence required covered by tests or analysis.
     * All tests are OK     * All tests are OK
     * All results of the checks are documented in a Software Configuration File, including     * All results of the checks are documented in a Software Configuration File, including
Line 39: Line 51:
       * module names       * module names
       * file checksums       * file checksums
 +
  
 ===== Pre-Release Rules ===== ===== Pre-Release Rules =====
  
-  * The copying of the software product and by-products to an online pre-release folder is executed by the bash file "spr".+  * The copying of the software product and by-products to an online pre-release folder is executed by the bash file 'distr.bat', 'distr.sh' or 'distr.zsh'.
   * A final end-test is executed to test   * A final end-test is executed to test
     * Download procedures     * Download procedures
Line 50: Line 63:
     * Availability of licensing information     * Availability of licensing information
     * Availability of disclaimers     * Availability of disclaimers
 +
  
 ===== Release Rules ===== ===== Release Rules =====
  
   * After successful final end test according to the pre-release rules,    * After successful final end test according to the pre-release rules, 
-    * the copying of the software product and by-products to an online release folder is executed by the bash file "sr".+    * the copying of the software product and by-products to an online release folder is executed by the bash file 'deploy.bat', 'deploy.sh' or 'deploy.zsh'
  
 +===== ✎ =====
 +~~DISCUSSION~~
codesnippets/verificationandvalidation.1665471771.txt.gz · Last modified: (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC0 1.0 Universal
CC0 1.0 Universal Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki