-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix: update tests after ikg modifications #172
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #172 +/- ##
==========================================
+ Coverage 71.21% 71.74% +0.52%
==========================================
Files 39 39
Lines 2321 2304 -17
==========================================
Hits 1653 1653
+ Misses 613 596 -17
Partials 55 55 ☔ View full report in Codecov by Sentry. |
409c977
to
a037dae
Compare
ingest/ingest_integration_test.go
Outdated
@@ -181,7 +149,7 @@ var _ = Describe("Ingestion", func() { | |||
Expect(err).To(Succeed()) | |||
Expect(resp2).NotTo(BeNil()) | |||
id2 := resp2.Info.Changes[0].Id | |||
Expect(id2).To(Equal(id)) | |||
Expect(id2).NotTo(Equal(id)) |
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.
Wait, so you ingest the exact same node twice, and receive different ids?
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.
yes the behavior changed: before, when you created the same node twice, it did not create a new one but was just updating the old one.
Now it is the contrary: it deletes the old one and creates a new one.
Same for Resources which are not DT: the behavior changed too.
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.
That's a huge bug if true, I'll check
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.
Confirmed, have a fix in my next PR
a037dae
to
f08f8d7
Compare
ingest/ingest_integration_test.go
Outdated
Expect(err).To(MatchError(ContainSubstring("server was unable to complete the request"))) | ||
Expect(resp3).To(BeNil()) |
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.
This is not the intended behavior!
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.
updated
@@ -125,7 +125,7 @@ var _ = Describe("Authorized", func() { | |||
resource1: PointTo(MatchFields(IgnoreExtras, Fields{ | |||
"Actions": MatchAllKeys(Keys{ | |||
action1: PointTo(MatchFields(IgnoreExtras, Fields{ | |||
"Allow": Equal(false), | |||
"Allow": Equal(true), |
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.
why did this need to change?
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.
change of data. The goal is to get the right 2 answers, whatever they are
Closing ENG-2397
f08f8d7
to
c59e1e6
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.
Approved, as long as the change in the AuthZ behavior actually was intended and needed to be changed in the test.
Closing ENG-2397