-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
JSTEP-10: Unify testing structure/tools #547
Comments
This was referenced Jan 11, 2025
@cowtowncoder Could you open this one up again? I made a mistake above PRs resolve this. Didn't know "partly resolves #xxx" would also do this 😅 |
Yeah, github is being too "smart". :-( |
This was referenced Jan 12, 2025
cowtowncoder
changed the title
JSTEP-10: Unifying testing structure/tools
JSTEP-10: Unify testing structure/tools
Jan 14, 2025
Completed, I think! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue serves as an umbrella issue for resolving [JSTEP-10: Unifying testing structure/tools]
TODO
failing
test utilsavro
module tests to JUnit 5 #549cbor
module tests to JUnit 5 #550ion
module tests to JUnit 5 #551protobuf
module tests to JUnit 5 #552smile
module tests to JUnit 5 #553/tofix
and remove existing/failing
funciontalityfailing
tests totofix
#554avro
module's/interop
tests at least)avro
module's/interop
tests at least) #555/interop
tests fromavro
module to JUnit 5How to do things
Change Code
@Test
by : Replace (by text) allpublic void test
to@Test \n public void test
public class
withimport org.jun... Test \n import static Asssertions.*; \n public class
Validate
public void test...
and check Dups or missing(indents)public class...
and check JavaDoc in between importsorg.junit.Assert
Assert.*
assertNotNull
error message String usageThe text was updated successfully, but these errors were encountered: