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.
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
Consider moving end2end tests to examples
or tests
#5
Comments
The tests were always a bit shaky on their concept, we wanted to be able to view the test cases we created while simultaneously hiding them from someone who just might want to have a look at common use cases in the I agree with you that moving the If everyone is onboard for the proposed changes I would like to add them with the release process for the next minor |
Finally managed to put everything together, the |
I am trying to update
cursive-tabs
to depend oncursive_core
rather thancursive
(cursive_core
is basicallycursive
without backends, so should be enough for libraries and have fewer breaking changes). Dependencies would still pull the fullcursive
crate.Currently end2end test binaries are in
src/bin/
. This means that they use the same dependencies as the library itself; but (like other tests) they require the fullcursive
crate and not justcursive_core
.(There is a RFC for per-bin dependencies, but it's not looking good yet, and probably not really the right thing™ anyway.)
Moving it to
tests
orexamples
would make them usedev-dependencies
.Another (probably better) solution is the
puppet-backend-tests
branch, which replaces these with direct individual tests.The text was updated successfully, but these errors were encountered: