-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Migrate to Angular's spec_bundle for tests. #6036
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
Changes from all commits
5b4c5cf
989cfa5
b9ae714
25c8413
6ba32ff
d763c56
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -313,7 +313,7 @@ describe('line_chart_v2/lib/scale test', () => { | |
| expect(scale.reverse([1000, 2000], [-100, 100], -100)).toBe(1000); | ||
| expect(scale.reverse([1000, 2000], [-100, 100], 100)).toBe(2000); | ||
|
|
||
| expect(scale.reverse([1000, 2000], [-100, 100], -101)).toBe(995); | ||
| expect(scale.reverse([1000, 2000], [-100, 100], -102)).toBe(990); | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This test started failing due to the migration. The underlying library doesn't seem to guarantee exact results -- it was returning 994 instead of 995 (maybe something to do with floating-point numbers?). Rather than just changing the expected value, I adjusted the test conditions so it continues to pass in a logical manner.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Understood. |
||
| expect(scale.reverse([1000, 2000], [-100, 100], 500)).toBe(4000); | ||
|
|
||
| expect( | ||
|
|
||
This file was deleted.
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 confused here. Why do all of our calls to tf_ng_web_test_suite already have a name specified when the old definition did not have name as a parameter?
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.
The
nameargument was previously captured by the**kwargsargument and automatically passed down to karma_web_test_suite unmodified. Now that we are usingnameargument explicitly in tf_ng_web_test_suite then we have to explicitly list it in the arguments here.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.
Ah that makes sense. Thanks.