-
Notifications
You must be signed in to change notification settings - Fork 11
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
Update integration tests to verify direct measurement results #1212
Update integration tests to verify direct measurement results #1212
Conversation
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
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.
Add integration tests for direct measurements.
nit: technically this isn't adding integration tests for direct measurements, but rather updating integration tests to verify direct methodologies.
Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @riemanli)
src/main/kotlin/org/wfanet/measurement/loadtest/measurementconsumer/MeasurementConsumerSimulator.kt
line 240 at r1 (raw file):
reachAndFrequencyResult.reach.noiseMechanism == NoiseMechanism.CONTINUOUS_GAUSSIAN ) .isTrue()
Suggestion:
assertThat(reachAndFrequencyResult.reach.noiseMechanism)
.isIn(listOf(NoiseMechanism.CONTINUOUS_LAPLACE, NoiseMechanism.CONTINUOUS_GAUSSIAN))
75fb61a
to
dce9004
Compare
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.
Thanks for the suggestion. Updated the title to reflect the real change.
Reviewable status: 0 of 5 files reviewed, 1 unresolved discussion (waiting on @SanjayVas)
src/main/kotlin/org/wfanet/measurement/loadtest/measurementconsumer/MeasurementConsumerSimulator.kt
line 240 at r1 (raw file):
reachAndFrequencyResult.reach.noiseMechanism == NoiseMechanism.CONTINUOUS_GAUSSIAN ) .isTrue()
Based on an offline discussion, we made the expected direct noise mechanism configurable from the constructor argument. That said, now the caller of the MC simulator needs to specified what the expected direct noise mechanism is according to their protocol config and EDP simulator setup.
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.
Reviewed 5 of 5 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @riemanli)
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.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @riemanli)
src/test/kotlin/org/wfanet/measurement/integration/k8s/SyntheticGeneratorCorrectnessTest.kt
line 47 at r2 (raw file):
/** * Test for correctness of an existing CMMS on Kubernetes where the EDP simulators use * [SyntheticGeneratorEventQuery] with [SyntheticGenerationSpecs.POPULATION_SPEC].
I believe you need to make the same note about assuming the simulators are using ACDP composition here.
dce9004
to
5eb5333
Compare
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.
Reviewable status: 4 of 5 files reviewed, 2 unresolved discussions (waiting on @SanjayVas)
src/test/kotlin/org/wfanet/measurement/integration/k8s/SyntheticGeneratorCorrectnessTest.kt
line 47 at r2 (raw file):
Previously, SanjayVas (Sanjay Vasandani) wrote…
I believe you need to make the same note about assuming the simulators are using ACDP composition here.
Thanks for catching that! Added.
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.
Reviewed 1 of 1 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @riemanli)
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.
Reviewed 4 of 5 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @stevenwarejones)
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.
Reviewed 4 of 5 files at r2, 1 of 1 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @riemanli)
5eb5333
to
b9e7911
Compare
No description provided.