-
Notifications
You must be signed in to change notification settings - Fork 17
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
Consolidate test vectors, add nextest filter #288
Conversation
crates/web5/src/test_vectors.rs
Outdated
} | ||
|
||
#[test] | ||
fn test_did_jwk_resolve() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also slight rename's in the two test names, but everything else is copy/pasta
if we move forward with this, then we need to rebase to retrieve the changes I just merged from #284 |
0a425f3
to
f83e121
Compare
0808ad9
to
4c0df0e
Compare
Alright this is done actually, rebase and moved the latest did:dht test vector into the single module as well |
crates/web5/src/test_vectors.rs
Outdated
} | ||
} | ||
|
||
mod presentation_definition { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice catch, fixed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea thanks! this is much better. I may have to make a change in the test runner depending on how much the xml changes but it should be quick and easy.
Thanks!
The original driving force for this was a failing CI. The CI was failing because our new
UnitTestSuite
solution isn't compatible with ournextest
configuration (best guess isnextest
is parallelizing things in a way wherein our solution doesn't work;cargo test
works fine so ourtest
CI job is passing without issues). We could probably find a way to configure thenextest
runner/harness such that it is indeed compatible, or we could use an external state file/env-var. But, I think we should consolidate test vectors regardless (IMO we think of test vectors as a singular suite of tests so it makes sense for them to exist in a single module), and if we do, then we can use thenextest
filter feature to only execute the test vectors in ourrust-test-vectors
CI job.@nitro-neal lmk what you think (please note, this PR is a merge into #283)