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

patched 'expect' should understand 'not' #139

Closed
juliemr opened this issue Oct 3, 2013 · 6 comments
Closed

patched 'expect' should understand 'not' #139

juliemr opened this issue Oct 3, 2013 · 6 comments

Comments

@juliemr
Copy link
Member

juliemr commented Oct 3, 2013

'expect' on promises currently doesn't understand the 'not' modifier.

@gsastry
Copy link

gsastry commented Oct 11, 2013

Is there an easy work around to this?

@Droogans
Copy link

@juliemr Please consider looking into this issue I've experienced as well:

Custom matcher not asserting in Astrolabe/Protractor + Jasmine test

I wonder if there's a relationship between .not causing issues, along with custom matchers acting strange.

@mvolkmann
Copy link

Is there an alternate to using .not.toBe ?

@juliemr
Copy link
Member Author

juliemr commented Nov 27, 2013

.not should be working on 0.13.0 and later.

@mvolkmann
Copy link

Thanks! I tried upgrading with "npm install protractor", but it gives lots of errors. See below. Maybe the package.json isn't quite right.

npm ERR! peerinvalid The package protractor does not satisfy its siblings' peerD
ependencies requirements!
npm ERR! peerinvalid Peer grunt-protractor-runner@0.1.1 wants protractor@~0.10.0

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "protractor" "--save-dev"
npm ERR! cwd C:\projects\gm-earnpower-client
npm ERR! node -v v0.10.18
npm ERR! npm -v 1.3.8
npm ERR! code EPEERINVALID

@juliemr
Copy link
Member Author

juliemr commented Nov 28, 2013

Looks like your grunt-protractor-runner isn't up to date with the new version. Can you try updating grunt-protractor-runner?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants