-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fixed insufficient inventory error message. #2056
Conversation
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.
Thank you
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
Thanks for the contribution. We've had an issue with our circle configuration which should be resolved now. Could you please rebase this on to master if you have a moment? |
This spec wasn't testing anything, it never confirmed the split it was setting up. The accept_alert errored on some drivers because no error was raised.
Previously, if a shipment split failed, the page would issue an alert(undefined). It would never alert with a proper error. This failed on the capybara selenium driver because it was confused about getting undefined. This replaces alert(undefined) with alert("Unable to complete split") Which is a little better (admittedly not much) for users, but doesn't confuse the selenium test driver.
Having text fields concatenated together is a poltergeist specific behaviour. Fortunately, asserting on the page title is a lot cleaner and just as effective.
Under selenium this spec wasn't working because it didn't click "ok" on the confirmation dialog. Also fixes a before block which wasn't running (which didn't affect the accuracy of the test, but did make it slightly slower).
Tests pass with things fixed up. Merging! |
No description provided.