Skip to content
This repository was archived by the owner on Jul 29, 2024. It is now read-only.

chore(test): remove jasmine addMatcher test #5072

Merged
merged 1 commit into from
Dec 6, 2018

Conversation

cnishina
Copy link
Contributor

@cnishina cnishina commented Nov 30, 2018

Removing the addMatchers test since we no longer support async calls
resolve with jasminewd since we removed jasminewd. Also Jasmine does
not appear to support async calls in custom expectations or the
compare method.

Copy link
Contributor

@heathkit heathkit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test no longer makes sense after jasminewd is gone. Let's just delete it.

- Removing the addMatchers test since we no longer support async calls
resolve with jasminewd since we removed jasminewd. Also Jasmine does
not appear to support async calls in custom expectations or the
compare method.
@cnishina cnishina changed the title chore(test): clean up jasmine addMatcher test chore(test): remove jasmine addMatcher test Dec 3, 2018
@cnishina
Copy link
Contributor Author

cnishina commented Dec 3, 2018

Removed the test.

@cnishina cnishina merged commit 3b7a3f7 into angular:selenium4 Dec 6, 2018
cnishina added a commit to cnishina/protractor that referenced this pull request Dec 19, 2018
- Removing the addMatchers test since we no longer support async calls
resolve with jasminewd since we removed jasminewd. Also Jasmine does
not appear to support async calls in custom expectations or the
compare method.
cnishina added a commit to cnishina/protractor that referenced this pull request Mar 23, 2019
- Removing the addMatchers test since we no longer support async calls
resolve with jasminewd since we removed jasminewd. Also Jasmine does
not appear to support async calls in custom expectations or the
compare method.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants