Open elizabethengelman opened 1 month ago
Hi @elizabethengelman can i work in this issue? I have experience with rust and testing👋🏻
Integration tests were not running properly, as mentioned in this issue. It was caused by help tests exiting suite early with exit code 0, therefore effectively ignoring all other tests. Help tests are fixed in #1734 and as the result failures are now visible:
failures:
build::build_all_when_in_non_package_directory
config::generate_key
config::multiple_networks
config::set_and_remove_global_network
config::set_and_remove_network
config::set_default_identity
config::set_default_network
config::use_default_futurenet
config::use_default_testnet
init::init
init::init_and_deploy
version::version
All failures are addressed and fixed in different PRs:
build
: #1736 config
+ version
: #1737init
: #1738
I noticed that when running
cargo test --package soroban-test --test it
locally, or in a GH Action, not all of the tests seem to run. The output looks like this:The output doesn't include the final test result including the number of failed and passed tests (i.e.
test result: FAILED, 31 passed; 10 failed;...
), nor does it include the status of all of the config tests, or any of the build, init, plugin, or version tests.After digging a little bit, it seems like something in the
help.rs
file is causing this, though I'm not 100% sure what is going on. It looks likehelp.rs
is potentially capturing the stdout (and maybe stderr too), so that the rest of the test output doesn't make it to the command line.I discovered this because there are a couple of tests that should be failing now, but they aren't.
Repo steps
To see this, comment out the tests in
help.rs
and you'll see that there are some failing tests. I'm not sure if all of them are valid failures, but the error inversion.rs
looks legit.