-
Notifications
You must be signed in to change notification settings - Fork 66
improve conformance comparison report for new tests #1833
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
Conversation
CROSS-COMMIT-REPORT-PARTIQLCORE ✅
Testing DetailsResult Details
CROSS-COMMIT-REPORT-PARTIQLEXTENDED ✅
Testing DetailsResult Details
|
test/partiql-tests-runner/src/test/kotlin/org/partiql/runner/ConformanceTestBase.kt
Outdated
Show resolved
Hide resolved
test/partiql-tests-runner/src/main/kotlin/org/partiql/runner/ReportAnalyzer.kt
Outdated
Show resolved
Hide resolved
test/partiql-tests-runner/src/main/kotlin/org/partiql/runner/ReportAnalyzer.kt
Outdated
Show resolved
Hide resolved
test/partiql-tests-runner/src/main/kotlin/org/partiql/runner/VersionProvider.kt
Outdated
Show resolved
Hide resolved
A quick link to the sample full conformance report |
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.
Please also update the PR title and description.
test/partiql-tests-runner/src/main/kotlin/org/partiql/runner/ReportAnalyzer.kt
Show resolved
Hide resolved
out.appendLine("- **Base Commit**: ${first.commitId}") | ||
out.appendLine("- **Target Commit**: ${second.commitId}") | ||
out.appendLine("- **Java Version**: ${VersionProvider.getJavaVersion()}") | ||
out.appendLine("- **PartiQL Version**: ${VersionProvider.getPartiQLVersion()}") |
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.
I can see value in printing the Java version but the PartiQL version is somewhat redundant since we already print out the base and target commits.
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.
It is listed in Dod of #1756. It should be fine as the version string is more straightforward.
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's no DoD for #1756. The "Additional Context" section that includes the java and partiql versions comes from the bug-report template -- https://github.com/partiql/partiql-lang-kotlin/blob/main/.github/ISSUE_TEMPLATE/bug-report.md#additional-context.
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.
Got it. I misunderstand the info. Just added java version as it might may helpful
import org.junit.jupiter.api.TestInstance | ||
import org.partiql.runner.test.TestRunner | ||
|
||
@TestInstance(TestInstance.Lifecycle.PER_CLASS) // Annotation is need to avoid skipList being recreated for each test. |
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.
Was this an issue before?
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.
No real issue for now. Can save a bit of time. Do you want to leave it as it was or is It Ok
private val passingFirstIgnoredSecond = first.passingSet.intersect(second.ignoredSet) | ||
private val failureFirstPassingSecond = first.failingSet.intersect(second.passingSet) | ||
private val ignoredFirstPassingSecond = first.ignoredSet.intersect(second.passingSet) | ||
private val newPassing = second.passingSet - first.passingSet - first.failingSet - first.ignoredSet |
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.
I am wondering why it shouldn't be newPassing = second.passingSet - first.passingSet
instead. e.g., test a
failed in the source (in first.failingSet
) but pass in target (in second.passingSet
). Should a
be a newPassing test in this case? Same for newFailing and newIgnored ones.
But the sample report result seems work well.
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.
We are collecting new tests added only. Anything in old test should not be included
Relevant Issues
Description
Other Information
License Information
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.