-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[core-http] fix browser tests on Firefox #9091
Merged
jeremymeng
merged 2 commits into
Azure:master
from
jeremymeng:core-http-firefox-test-failure
May 27, 2020
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,20 +9,22 @@ describe("XML serializer", function() { | |
describe("parseXML(string)", function() { | ||
it("with undefined", async function() { | ||
const error: Error = await msAssert.throwsAsync(parseXML(undefined as any)); | ||
assert.notStrictEqual( | ||
error.message.indexOf("Document is empty"), | ||
-1, | ||
`error.message ("${error.message}") should have contained "Document is empty"` | ||
assert.ok( | ||
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. is it worth checking this message? Should we just assert that it throws? 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. I wanted to keep the old behavior of verifying that it's a parsing error. |
||
error.message.indexOf("Document is empty") !== -1 || // Chrome | ||
(error.message.startsWith("XML Parsing Error: syntax error") && | ||
error.message.indexOf("undefined") !== -1), // Firefox | ||
`error.message ("${error.message}") should have contained "Document is empty" or "undefined"` | ||
); | ||
}); | ||
|
||
it("with null", async function() { | ||
// tslint:disable-next-line:no-null-keyword | ||
const error: Error = await msAssert.throwsAsync(parseXML(null as any)); | ||
assert.notStrictEqual( | ||
error.message.indexOf("Document is empty"), | ||
-1, | ||
`error.message ("${error.message}") should have contained "Document is empty"` | ||
assert.ok( | ||
error.message.indexOf("Document is empty") !== -1 || // Chrome | ||
(error.message.startsWith("XML Parsing Error: syntax error") && | ||
error.message.indexOf("null") !== -1), // Firefox | ||
`error.message ("${error.message}") should have contained "Document is empty" or "null"` | ||
); | ||
}); | ||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
bizarre to me that we're worried about times thousands of years from the present
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.
yeah, I will update to some date in 2020