Pytest integrated#3331
Conversation
matching either to a file named `test_foo.py`.
Native configuration is x86_64-pc-linux-gnu
=== tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
=== Summary === to in CMakeLists.txt
so that the `input` directory is found.
so that the `test` directory is found.
so that the `data` directory is found.
Fails due to missing file `grid.fci.nc`.
Change directory to exe location prior to attempting to run it.
Change directory to exe location prior to attempting to run it.
Change directory to exe location prior to attempting to run it.
This is used in `run_integrated_tests.sh` to determine the verbosity level for pytest.
to prevent type-checker warnings.
303d76c to
b6b4e1c
Compare
9cf1c95 to
3e91b3a
Compare
Use a fixture for benchmark data.
Use a fixture for benchmark data.
3e91b3a to
7f920ac
Compare
dschwoerer
left a comment
There was a problem hiding this comment.
It seems one of the MMS tests is missing. That certainly needs fixing.
I find it also increadibly hard to review, as in some case the rename from runtest to test_* is not rendered correctly on github. In some cases this seems to be done such that git itself is not aware of the the rename, e.g. test-fci-mpi/runtest.
This makes it even harder to figure out what was changed, as you clearly did not write the whole test new.
I have reviewed test-fci-mpi/runtest more carefully, and it is doing only part what is in next. It is skipping the iteration over the different test cases:
https://github.com/boutproject/BOUT-dev/blob/next/tests/integrated/test-fci-mpi/runtest#L49
Also, it would only output the errors after the assert:
So this is never printed.
| # Requires: netcdf | ||
| # Requires: not metric_3d | ||
| # Cores: 4 | ||
|
|
There was a problem hiding this comment.
I doubt the current test system still parses and process them, so the can be removed?
|
I forgot - the new pytest is much faster, which is nice, but I am wondering this comes from skipping tests. |
No description provided.