-
-
Notifications
You must be signed in to change notification settings - Fork 770
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
Avoid running test for #1456 on Safari #1481
Conversation
286b0a2
to
54f67c1
Compare
test/issues/issues-test.js
Outdated
describe("#1456", function () { | ||
if (throwsOnUnconfigurableProperty) { return; } |
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.
Any reason not to do this all inline instead of setting a single-use variable?
Also if you do the check in the beforeEach
, you can call this.skip();
to skip all the related tests.
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.
nope, it was a quick and dirty thing, and I wasn't aware of the this.skip thing.
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.
@fatso83 will you make a slow and clean version, or shall we merge this one?
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, sorry, I totally forgot. Was offline and on holiday for a week.
96023d8
to
3642905
Compare
3642905
to
bb2d585
Compare
I think the issues have been addressed, @fearphage. I started moving the test for error throwing to |
bb2d585
to
24d15f2
Compare
👍 |
Purpose
This avoids breaking the build by avoiding running the breaking test on Safari. See background in #1462.
Background (Problem in detail) - optional
Safari throws an error when trying to configure properties on
window
that are not configurable. AFAIK this is not a problem Sinon can solve: if the prop cannot be stubbed, then we shouldn't suppress the error or avoid trying to stub it.How to verify - mandatory
npm install
npm run test-cloud
BTW, the code is not so nice ATM. I was just so annoyed by the errors from Travis, so just needed to put a fix out there ... Not totally sure where to put the runtime detection of how this breaks and I am not so sure about how I skip the test. Maybe a simple
return
would suffice?