This document discusses asynchronous web testing and contains chapters on JavaScript concepts like scope, closures, callbacks, and promises which are important for understanding async JavaScript. It also has chapters on related industry tools and frameworks for testing like Angular, Protractor, Jasmine, and discusses issues with using Selenium to test Angular applications. The concluding chapter emphasizes that Angular UI tests are best developed in JavaScript to leverage its promises and that page objects can be used but calls must be managed carefully.

1. Async web testing
The pain and the antidote

3. Don’t forget to …

4. Some quick theory
Chapter 1
* Javascript scope
* Javascript closure
* Javascript callbacks
* Angular promises

5. Some quick theory
Chapter 1
* Javascript scope
* Javascript closure
var add = (function () {
var counter = 0;
return function () {return counter += 1;}
})();

6. Some quick theory
Chapter 1
browser.wait(function () {
return notification.getText().then(function (tex
return text === aMessage;
});
}, standardPageTimeout, "aMessage should be " +
aMessage);
* Javascript callbacks

7. Some quick theory
Chapter 1
$http.get("/api/my/name")
.then(
// success
function(response) {
console.log("Your name is: " + response.data);
},
// failure
function(error) {
console.log("The request failed: " + error);
});
* Angular promises

8. Some quick theory
Chapter 1
* Angular promises, some fun aspects
1. Promises are a core Angular feature
2. They are async
3. In async js, we return control to the browser
4. We call something when a promise has a result
5. That particular ‘when’, we know nothing about
6. Of course, read more please :)
7. Without understanding these, you’ll fail

9. Some industry
Chapter 2
node.js angular
karma
protractor
jasmine
reporte
rs
restful
node
runner
underscore.js
grunt

10. Some industry
Chapter 2
About the ‘findElement’ problem … and
how it trashes ‘Page Objects’ setup
when testing Angular

11. Some industry
Chapter 2
Let’s see our Chapter 1 stuff in ‘Industry’

12. Some conclusions
Chapter 3
enium, at its current versions, is not enough to test angu
ar UI tests must be developed in JS, to benefit from its p
bjects can still be used, but careful not to drown in a call

14. Some conclusions
Chapter 3
Many thanks for attending !!!
Is great to meet you all !!!