scenario runner should allow future value as argument

[vojtajina]

it('async expectation', function() {
  browser().navigateTo('index.html');

  var countBefore = element('ul#test li').count();

  // here is code which adds a node

  // this does not work - the future has no value yet
  expect(element('ul#suck li').count()).toEqual(count.value + 1);
});

This this topic for more info: https://groups.google.com/forum/#!topic/angular/FszMlvnrQfY

[juliemr]

Ping! This would be awesome.

[co-dh]

My personal feeling about the scenario is that it's a bad abstraction.
It's a surprise that .count() is not return a number,
and worse, you cannot do expect(1).toEqual(1).
I think the DSL is intended to hide asyn call, but the code still looks like imperative, and very count intuitive.

Overall, Angular.js is awesome!

[Elexy]

I now use this in my scenario:

function appWindow() {
    return document.getElementsByTagName('iframe')[0].contentWindow;
}
function appAngular() {
    return appWindow().angular;
}
...
it('should create a tab', function () {
    var pageCount = appAngular().element('.page_navigation li').length;
    console.log(repeater('.page_navigation li').count().exec)
    element('a.add-page-link').click();
    expect(repeater('.page_navigation li').count()).toBe(pageCount+1);
});

Is that the right way until this is implemented?

[btford]

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!