Protractor v0.12.1 Release Notes
-
🚀 Note: Major version 0 releases are for initial development, and backwards incompatible changes may be introduced at any time.
Minor features
👍 (201b59c) feat(jasminewd): better error messaging when expect is called with a WebElement
✅ (d383770) feat(clientsidescripts): better error reporting from testForAngular and waitForAngular
🐛 Bug fixes
- ⚡️ (8580c0c) fix(install-selenium): update to chromedriver 2.6
Update to the latest version of Chromedriver. This fixes the issue with OS X 10.9. Closes #181.
✅ (ebc528f) fix(debugging): switch debugging tests to the new test app urls.
✅ (8ff4787) fix(runner): exit with proper code when tests fail
When errors with messages matching /timeout/ were created, Protractor clears the control flow so that the remainder of the tasks scheduled for that spec don't bleed over into the next spec. This was messing up the promises used in the runner, since they are also webdriver promises. Long term, the runner should not use webdriver promises. For now, fix by having the runner resolve promises directly rather than through chaining, and add a TODO to use promises which aren't connected to WebDriver's control flow in the runner.
Closes #214.
↪ (81501c5) fix(clientsidescripts): workaround for IE 8 "async page reload" init problem
0️⃣ (21264fd) fix(find): fix error when exposed to ng-options element with a default option
Protractor will now ignore elements with the ng-bind class that don't have a proper binding on their data, instead of blowing up when encoutering them.
Closes #165, may fix #170
- (f672648) fix(findelements): fix isPresent for repeaters by row for real
💥 Breaking Changes
- 🚚 (bf5b076) fix(cli): remove boolean verbose and stack trace options
Also add better description for what the command line options are.
Tiny breaking change: Rename the 'includeStackTrace' command line option to 'stackTrace' for brevity.