Changes between Version 21 and Version 22 of addnewNR
- Timestamp:
- 01/30/26 12:48:40 (3 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
addnewNR
v21 v22 3 3 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. 4 4 5 If a new capability is being added to ISSM, it is * critical* that a new test is created.5 If a new capability is being added to ISSM, it is **absolutely critical** that a new test is created. 6 6 7 7 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). … … 93 93 In the case of a brand new test 94 94 {{{ 95 svnadd test/NightlyRun/testXXX.m test/NightlyRun/testXXX.py test/Archives/ArchiveXXX.arch95 git add test/NightlyRun/testXXX.m test/NightlyRun/testXXX.py test/Archives/ArchiveXXX.arch 96 96 }}} 97 97 then, 98 98 {{{ 99 svn commit –m "NEW: Added test to check ...”` 99 git commit –m "NEW: Added test to check ..." 100 git push 100 101 }}} 101 102 with an appropriate message. Otherwise you can simply update the archive and commit the changes.
![(please configure the [header_logo] section in trac.ini)](/trac/issm/chrome/common/trac_banner.png)