-
Notifications
You must be signed in to change notification settings - Fork 365
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reorganize unit tests based on discussion with Jim Edwards
My original idea had been to have a 'tests' subdirectory of each production code directory, and to have unit tests live there. However, Jim Edwards suggested having a top-level tests directory, and then having a directory structure under that that mirrors the production code directory structure. This commit does that. Note that I have also moved case_fake.py to a higher level within the tests directory, mirroring the location of case.py. Test suite: python -m unittest discover -s CIME/tests -t . Test baseline: N/A Test namelist changes: N/A Test status: pass Fixes: None User interface changes?: No Code review: None
- Loading branch information
Showing
10 changed files
with
17 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
The directory structure of this tests directory mirrors the directory structure | ||
of the parent (production code) directory. | ||
|
||
So, for example, unit tests for CIME/foo.py should live in | ||
CIME/tests/test_foo.py, and unit tests for CIME/SystemTests/bar.py should live | ||
in CIME/tests/SystemTests/test_bar.py. |
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
Empty file.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters