Changes between Version 31 and Version 32 of FpCtbtoOverview

Timestamp:

Apr 6, 2016, 7:41:47 AM (8 years ago)

Author:

dearn

Comment:

--

FpCtbtoOverview

@@ -109 +109 @@
         * Other minor changes meant to get the testing environment up to speed for beginning Work Package 8 included the addition of nested input test cases, as well as general code ehancements 
 
-    * One of the major problems that was facing our testing environment was that it had a broad collection of test cases - many with poor naming conventions - and we frequently got confused over which cases should be run, or had been run, after majour project milestones.  We realized that we wanted the general FLEXPART user to be able to run a single command and have a comprehensive set of tests performed, giving an immediate (within 2-15 minutes, depending on depth of tests) indication of whether the system was running correctly or not.  Anything short of this would make it difficult to encourage the discipline of Test Driven Development (TDD) and frequent testing of the system after modifications  A description of this enhancement is described in  '''[ADD WIKI PAGE]'''
+    * One of the major problems that was facing our testing environment was that it had a broad collection of test cases - many with poor naming conventions - and we frequently got confused over which cases should be run, or had been run, after majour project milestones.  We realized that we wanted the general FLEXPART user to be able to run a single command and have a comprehensive set of tests performed, giving an immediate (within 2-15 minutes, depending on depth of tests) indication of whether the system was running correctly or not.  Anything short of this would make it difficult to encourage the discipline of Test Driven Development (TDD) and frequent testing of the system after modifications  A description of this enhancement is described in  [wiki:FptestenvConsolidation Consolidation of tests] 
 
     * The existing test environment documentation was reviewed and modified.  A number of cosmetic and code-based changes were made, but the primary changes came from the realization that the documentation was very technical, and would be difficult for new users to understand.  Therefore, the primary document, '''[ADD  LINK]''' was modified with two links at the beginning which pointed to more "hands-on" documents, including a quick-start page '''[ADD  LINK]'''. Note - these two pages are best viewed in a browser with a markdown extension.