Profile cover photo
Profile photo
Mirco Zeiss
75 followers
75 followers
About
Mirco's posts

Post has attachment

new blog post online - http://www.mircozeiss.com/collaborative-todo-app-with-jet/ - Collaborative Todo-App with Jet

Post has attachment

Post has attachment

Post has attachment

Post has shared content
Just pushed version 0.24.0 of Protractor. This is a big change with lots of breaking stuff, so please read the changelog! Summary of the breaking changes below.

We removed some locators which have been deprecated for a while. by.input, by.select, by.textarea are all gone now, and can be replaced with by.model. 

The process around launching multiple tests and sharding tests has been updated. The option to splitTestsBetweenCapabilities wasn't quite what we wanted, and has been removed. Instead, each individual capability will control its own behavior - whether it is sharded or not, how many times to run the test suite, and how many instances can be used for sharding. The reference configuration file has full info on how to do this: https://github.com/angular/protractor/blob/master/referenceConf.js#L75

And finally, we've done a big refactor of how WebElements and ElementFinder works. This should be largely transparent if you're using the element() function. 

Our problem previously was a lot of confusion around what was a WebElement, what was a wrapped WebElement, what was an ElementFinder, and when any of the things should be used and when they actually contacted the browser. 

Now, there are only two classes. A WebElement is the unmodified object from WebDriverJS. You can find one using `browser.findElement()`.

The other class is the ElementFinder. This is the object returned by `element(by.binding('foo'))`. ElementFinders can be chained, like so: `element(by.css('.container')).element(by.binding('foo'))`. ElementFinders support arrays, such as `element.all(by.tagName('li')).last()`. Setting up ElementFinders like this does not actually perform any action on the browser, so you can define how to find your elements in helper files without worrying about the state of your application.

ElementFinders have all of the action methods available on WebElements - like getText, click, and sendKeys. At the point where one of these is called a request actually goes out to the browser to find the element.

You are now able to chain actions on ElementFinders - such as `element(by.model('name')).clear().sendKeys('bob')`.

From an ElementFinder, you can always get at the described WebElement with `element(locator).getWebElement`. In general, you should never have to do this - just use ElementFinders and actions on them.

We hope these changes make using WebElements and ElementFinders more clear. As always, if you have issues with the new release, please report on GitHub, and enjoy!

Post has attachment

Post has attachment

Post has attachment

Post has shared content
Just released +AngularJS v1.3.0-beta.2 silent-ventriloquism!

Thanks to all these contributors:
Basem Mostafa, Chung-Min Cheng, Igor Minar, Jeff Cross, Louis Haußknecht, Matias Niemelä, Narretz, Nick Carter, Nick Heiner, Pawel Kozlowski, Peter Bacon Darwin, Sagie Maoz, Stéphane Reynaud, Thomas Belin, Tobias Bosch, Tomer Chachamu, Vojta Jina, Wesley Cho, chadfennell, doodeec.

Changelog:
https://github.com/angular/angular.js/blob/master/CHANGELOG.md#130-beta2-silent-ventriloquism-2014-03-14

#angularjs   #release
Wait while more posts are being loaded