- Notifications
You must be signed in to change notification settings - Fork401
loco test bug fix#423
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…ogrifAI into LocoTestRefactormerge master
codecovbot commentedOct 16, 2019 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov Report
@@ Coverage Diff @@## master #423 +/- ##===========================================- Coverage 86.94% 26.52% -60.43%=========================================== Files 340 337 -3 Lines 11388 11131 -257 Branches 363 593 +230 ===========================================- Hits 9901 2952 -6949- Misses 1487 8179 +6692
Continue to review full report at Codecov.
|
tovbinm left a comment
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 would it not pick any features?
| it("should pick between1 and 4 of the features") { | ||
| all(parsed.map(_.size)) should (be>=1 and be<=4) | ||
| it("should pick between0 and 4 features") { | ||
| all(parsed.map(_.size)) should (be>=0 and be<=4) |
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 seems like it is not checking very much... can you do a check for the conditions described above and then do the size check?
AdamChit commentedOct 19, 2019
So in the test the labels are generated based on the PickList feature: And all the features have a chance of being empty: One case that could happen: Note: the chance of this happening is very low which explains why it doesn't always appear in the CI build. |
tovbinm commentedOct 19, 2019
@AdamChit are you still working on adding a more robust test? |
tovbinm commentedJan 9, 2020
any updates?@AdamChit |
Related issues
test refactor made in#412 causes one of the test cases to fail.
Specially this test assumed that at-least 1 of the 4 features would be selectedhttps://github.com/salesforce/TransmogrifAI/blob/master/core/src/test/scala/com/salesforce/op/stages/impl/insights/RecordInsightsLOCOTest.scala#L236
Describe the proposed solution
Test should allow the case where none of the features are picked
Additional context

example of the test failing: