it will useful to use these outside of ancestors, too.
Details
- Reviewers
kevincox - Group Reviewers
hg-reviewers - Commits
- rHG168041fa6d5f: rust: factorized testing Graphs
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Queued the series, thanks.
+++ b/rust/hg-core/src/testing.rs
Maybe we can add separate test files, but I don't know which is preferred.
https://doc.rust-lang.org/book/ch11-03-test-organization.html#submodules-in-integration-tests
@yuja the doc you're linking is about integration tests, so it wouldn't apply to these tests which are really unitary in my mind. Usually the main difference would be the access to the private constructs that the integration tests can't perform, but it's true that most of these implementations are public anyway.
@yuja the doc you're linking is about integration tests, so it wouldn't apply to these tests which are really unitary in my mind. Usually the main difference would be the access to the private constructs that the integration tests can't perform, but it's true that most of these implementations are public anyway.
Yep, I tend to ignore the theoretical meanings of unit vs integration, and
use them as test frameworks fit to small/simple and big/complex tests
respectively.
I just don't know if that's common in Rust community.