Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Testing Ext JS 5 Apps with Siesta

Testing Ext JS 5 Apps with Siesta

Slides from my talk at the Ext JS 1 day conference in Milan

Mats Bryntse

October 01, 2014
Tweet

More Decks by Mats Bryntse

Other Decks in Programming

Transcript

  1. Webinar | Content Unit tests UI tests Continuous Integration •

    Writing a unit test • Using PhantomJS • Hello world sample • Event recorder intro • Testing an Ext JS cmp • Recording a UI test • TeamCity • Code Coverage • Statistics • Cloud Testing
  2. Intro | WHY 1. Productivity & confidence in code 2.

    Frameworks contain bugs 3. So does your code (and mine) 4. Refactoring & code handover 5. Fix bugs once
  3. Unit tests | Intro •Should be your #1 priority •Cover

    your most important JS classes •Run often, before commit, daily, nightly. •Use TDD approach + BDD style for readability
  4. Unit tests | TDD basics 1. Make the unit test

    fail 2. Implement 3. Make the test pass 4. Refactor, Repeat
  5. UI tests | Event recorder •Records user actions: clicks, types,

    drag drop •Exports actions to a Siesta test case •Can be used by a non-programmer •Big timesaver
  6. Continuous Integration | Intro •Bryntum uses TeamCity, Siesta integrates with

    others (Jenkins…) •Test suites run every 2 hours in Chrome •Full test suites executed nightly •Reports, statistics, charts and code coverage
  7. Continuous Integration | Cloud testing •Need to create Virtual Machines

    for each version of IE •Total: Chrome, Safari, FF, IE 7-11 => 7 VMs •Managing such a farm can be very time consuming
  8. Continuous Integration | Cloud testing •Siesta integrates with both BrowserStack

    and Sauce Labs •Run tests easily in any OS and Browser combination •No need to setup your own VM farm •Read more on the Bryntum blog…