Skip to content

Mv the directory src/tests to test #669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 31, 2022
Merged

Mv the directory src/tests to test #669

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0b3ac52
mv src/tests to test
jvdp1 Jul 26, 2022
6e9d48b
adapt script fpm
jvdp1 Jul 26, 2022
2829e2d
update md files
jvdp1 Jul 26, 2022
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
update md files
  • Loading branch information
@jvdp1
jvdp1 committed Jul 26, 2022
commit 2829e2d517a142c98bbf20297768a299cce4c84d
4 changes: 2 additions & 2 deletions STYLE_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,9 @@ This style guide is a living document and proposed changes may be adopted after
* If the interface and implementation is split using submodules the implementation submodule file should have the same name as the
interface (parent) module but end in `_implementation`
E.g., `string_class.f90` and `string_class_implementation.f90`
* Tests should be added in the `tests` subdirectory and have the same name as the module they are testing with the `test_` prefix
* Tests should be added in the `test` subdirectory and have the same name as the module they are testing with the `test_` prefix
added
E.g., `string_class.f90` and `tests/test_string_class.f90`
E.g., `string_class.f90` and `test/test_string_class.f90`

## Indentation & whitespace

Expand Down
4 changes: 2 additions & 2 deletions WORKFLOW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ To add tests, the macro ``ADDTEST`` should be used instead of the CMake function
``add_test``, the macro hides creation of the executable target, linking against the
main library target and registering the test.
The tests themselves are defined as standalone executables in the subdirectories
in ``src/tests``, a new subdirectory with tests has to be registred in
``src/tests/CMakeLists.txt``.
in ``test``, a new subdirectory with tests has to be registered in
``test/CMakeLists.txt``.

The source tree should be considered read-only. References to ``PROJECT_SOURCE_DIR``
and ``CMAKE_CURRENT_SOURCE_DIR`` should only be used for accessing source files,
Expand Down
4 changes: 2 additions & 2 deletions doc/specs/stdlib_hash_procedures.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1623,7 +1623,7 @@ various hash functions. The other is a comparison of the outputs of
the Fortran hash functions, with the outputs of the C and C++ hash
procedures that are the inspiration for the Fortran hash functions.

In the `src/test/hash_functions_perf` subdirectory, the Fortran Standard
In the `test/hash_functions_perf` subdirectory, the Fortran Standard
Library provides two performance test codes for
the hash functions of `stdlib_hash_32bit` and
`stdlib_hash_64bit`, `test_32_bit_hash_performance` and
Expand Down Expand Up @@ -1726,7 +1726,7 @@ severely impact the performance of `nmhash32`, `nmhash32x`,
`water_hash`, `pengy_hash`, and `spooky_hash` relative to
`fnv_1_hash` and `fnv_1a_hash`.

In the `src/test/hash_functions` subdirectory, the Fortran
In the `test/hash_functions` subdirectory, the Fortran
Standard Library contains codes to test the validity of
the Fortran codes against the original C and C++ codes. It consists of one
executable `test_hash_functions` that
Expand Down