Testing is an important part of all software projects – and so is keeping sane. In order to not make the developers and testers lose their minds while verifying that a huge amount of features still work, the testing should be automated. What’s worse, the complexity of the underlying technologies often make it more challenging to test web applications than conventional software. This talk will show you some tools and methodologies for automated testing of web apps and especially the user interface layer of web apps. It will discuss how to architect a web app for easy testing and what kind of tests should go where and in which situation. We’ll even have a look at how the customer requirements can be automatically tested and verified to work – exactly as specified by the ones paying the bills.

1. A U T O M AT E D T E S T I N G
O F W E B A P P S
+Jonatan Kronqvist @zch

4. }>

6. A G E N D A
• Software testing in general
• Architecting for testability
• Testing web UIs
• What should I do?

7. A G E N D A
• Software testing in general
• Architecting for testability
• Testing web UIs
• What should I do?

9. Unit Testing

10. Integration Testing

11. System Testing

12. Regression Testing

13. End-to-End Testing

14. Acceptance Testing

15. Load Testing

16. Create VALUE for Your Customers

17. – J O H N D O E V E L O P E R
“Unit testing is a waste of time, because the tests
don't prove that things work correctly”

19. Red
Green
Refactor

20. 1. You will ALWAYS have code that worked a minute ago
2. You will have more and more automatic tests that can be
run all the time
3. You will have usage examples for all of your code and API
4. All your code will be testable by default

21. Best ROI:
• integration
• regression
• system

22. Most unit tests could be
replaced by assertions

23. Focus on continuous integration
and system testing

24. B E H AV I O R D R I V E N D E V E L O P M E N T

25. Scenario 1: Account has sufficient funds
Given the account balance is $100
And the card is valid
And the machine contains enough money
When the Account Holder requests $20
Then the ATM should dispense $20
And the account balance should be $80
And the card should be returned

26. 1. Easy to define end-to-end behavior to be tested
2. Business value easily translates to this format
3. You're probably already defining user stories

27. A G E N D A
• Software testing in general
• Architecting for testability
• Testing web UIs
• What should I do?

29. • Cross browser differences
• Logic that depends on the DOM
• Asynchronous execution
• Possibly slow execution

30. M V P
Presenter
Model
(State)
View
Rendering
logic
Event
handling
logic

31. Avoid new – Dependency Injection

32. A G E N D A
• Software testing in general
• Architecting for testability
• Testing web UIs
• What should I do?

34. Unit Testing?

35. Integration Testing?

36. System Testing?

37. End-to-end Testing?

38. Web automation

39. BDD framework + Selenium or Vaadin
TestBench

41. Narrative:
As a user
I want to perform calculations
So that I can easily get the results without
calculating in my head
Scenario: Calculate 1+2
Given I have the calculator open
When I push 1+2
Then the result should be 3.0

42. public class CalculatorSteps extends TestBenchTestCase {
private WebDriver driver;
private CalculatorPageObject calculator;
@BeforeScenario
public void setUpWebDriver() {
driver = TestBench.createDriver(new FirefoxDriver());
calculator = PageFactory.initElements(driver,
CalculatorPageObject.class);
}
@AfterScenario
public void tearDownWebDriver() {
driver.quit();
}

43. @Given("I have the calculator open")
public void theCalculatorIsOpen() {
calculator.open();
}
@When("I push $buttons")
public void enter(String buttons) {
calculator.enter(buttons);
}
@Then("the result should be $result")
public void assertResult(String result) {
assertEquals(result, calculator.getResult());
}
}

44. public class SimpleCalculation extends JUnitStory {
@Override
public Configuration configuration() {
return new MostUsefulConfiguration()
.useStoryLoader(new LoadFromClasspath(this.getClass()))
.useStoryReporterBuilder(new StoryReporterBuilder()
.withDefaultFormats()
.withFormats(Format.CONSOLE, Format.TXT));
}
@Override
public InjectableStepsFactory stepsFactory() {
return new InstanceStepsFactory(configuration(),
new CalculatorSteps());
}
}

46. }>
>2500 tests
<15 minutes
each commit

47. Load Testing

48. A G E N D A
• Software testing in general
• Architecting for testability
• Testing web UIs
• What should I do?

49. WHAT SHOULD I DO?

50. Architect for testability and flexibility

51. Focus on Integration, End-to-end and System
Tests

52. Try TDD, but don't sweat it

53. Use BDD

54. Don't forget to load test!

55. ENSURE VALUE IS CREATED
FOR YOUR CUSTOMERS

56. Q & A
Please rate the presentation at
gwtcreate.com/agenda

57. I M A G E S U S E D
• https://flic.kr/p/671Z4A
• https://flic.kr/p/bsozXc
• https://flic.kr/p/hRfBC
• https://flic.kr/p/nQ7ac5
• https://flic.kr/p/8sf5Xt
• https://flic.kr/p/4LH5Eo
• https://flic.kr/p/7Lx9Kk
• https://flic.kr/p/nAi4GZ
• https://flic.kr/p/eguHX8
• https://flic.kr/p/4fmu9E
• https://flic.kr/p/dtSHid
• https://flic.kr/p/bwpVQ7
• https://flic.kr/p/fGyo6Q