Changes between Version 20 and Version 21 of addnewNR

Timestamp:

09/29/23 06:54:47 (16 months ago)

Author:

Mathieu Morlighem

Comment:

--

addnewNR

@@ -1 +1 @@
  == Introduction ==
 
-ISSM relies on regression tests to check that no bug is introduced during code development. All the tests are located in `$ISSM_DIR/test/test/NightlyRun` and all the tests whose number are less than 1000 are run after each change pushed to the svn repository (through jenkins: https://ross.ics.uci.edu/job/Linux_Ubuntu/) and 4 times a day (through cron jobs). See [wiki:jenkins] for more information.
+ISSM relies on regression tests to check that no bug is introduced during code development. All the tests are located in `$ISSM_DIR/test/test/NightlyRun` and all the tests whose number are less than 1000 are run after each change pushed to the svn repository (through jenkins: https://ross.ics.uci.edu/jenkins/). See [wiki:jenkins] for more information.
 
-If a new capability is being added to ISSM, it is critical that a new test is created.
+If a new capability is being added to ISSM, it is *critical* that a new test is created.
 
-These nightly runs are not meant to be realistic. They rely on very coarse meshes. We only want to check that the numerics has not changed, the results are obviously meaningless. Each test should take less than 10 seconds to run.
+These nightly runs are not meant to be realistic. They rely on very coarse meshes. We only want to check that the numerics has not changed, the results are obviously meaningless. Each test should take less than 10 seconds to run (ideally 1 second).
 
  == Running a test ==
@@ -97 +97 @@
 then,
 {{{
-svn commit –m "ADD: Added test to check ...”`
+svn commit –m "NEW: Added test to check ...”`
 }}}
 with an appropriate message. Otherwise you can simply update the archive and commit the changes.