The document outlines the features and roles associated with Sencha Test versions 2.0, 2.1, and 2.2, highlighting the needs and dreams of developers, QA engineers, and DevOps engineers regarding application testing. Key features include in-browser testing, improved API functionalities, automated test creation, visual screen comparisons, and CI integration. The latest updates focus on enhancing code maintainability, allowing the use of external libraries, and supporting ExtReact applications.

2. What’s new in Sencha Test?
Olga Petrova

3. Agenda
• Sencha Test Roles
• Sencha Test 2.0 features
• Sencha Test 2.1 features
• Sencha Test 2.2 features
• Demo

4. Sencha Test Roles

5. Roles
• Developer
• QA Engineer
• DevOps Engineer

6. Developer Tom

7. Tom’s dreams
• Less bugs
• Easy refactoring
• Better code understanding
• Better code design

8. Tom’s problems
• Application complexity
• Asynchronous nature
• Hard to mock
• Short release time

9. QA Engineer Alice

10. Alice’s dreams
• Easy test writing automation
• Good code coverage
• Defense against regressions

11. Alice’s problems
• Uncontrollable environment
• Application complexity
• Asynchronous nature
• Short release time

12. DevOps Engineer Steve

13. Steve’s dreams
• More confidence in the code, less fear about releases
• Easy releases automation
• Be able to release at any time

14. Steve’s problems
• Integration of automated tests into CI environment
• Short release time

15. Sencha Test 2.0 features

16. Runtime environment
In-Browser
• Single-page application
• Run application and tests in browser
• Run in several browsers
simultaneously
Web Driver
• Multi-page application
• Run tests outside of the browser using
WebDriver
• Test any web applications
Developer
QA Engineer

17. Sencha Test API
• Component/Element future wrapper
- ST.grid()
- ST.component()
- ST.element()
• Calls that wait for the component to be in a certain state
- .rendered()
- .disabled()
• Actions
- .click()
- .type(’mytext')
Developer
QA Engineer

18. Sencha Test API
• Assertions
- .expect('value').toBe('test-username')
- .expect('innerHTML').toContain('my-container')
- .expect('visibility').toBe('visible')
- .get('height') .and(function () {
expect(this.future.data.height).toBe(200);
}))
Developer
QA Engineer

19. Sencha Test API
• New features for WebDriver tests:
- ST.execute
- ST.navigate
Developer
QA Engineer

20. Event Recorder
• Faster test creation
• Improved element locator strategies lets to avoiding the use of dynamic IDs
• Choosing component locator strategy
• Editing values in recorded script
QA Engineer

21. Visual Screen Comparison
• Visual comparison of application screenshots generated in different browsers:
- ST.screenshot
• Fixed screen size settings for visual testing
QA Engineer

22. Code Coverage
• Build-in integration with Istanbul
• Detailed report for your application code
QA Engineer

23. Selenium server and Browser farms
• Integration with browser farms
• Integration with Selenium WebDriver
• Embedded Selenium Server and Browser (Chrome)
DevOps Engineer

24. Archive Server
• Review and Analyze Test Results from Multiple Runs
• Remote and Local Archive Servers
DevOps Engineer

25. Continuous Integration CI
• Integration with Jenkins and Team City
• Command Line Interface (CLI)
• Store results from multiple Continuous Integration (CI) runs
DevOps Engineer

26. Sencha Test 2.1 features

27. Sencha Test Inspector
• Find stable and meaningful component locators
• Paste locators directly into the test code or create page object
Developer
QA Engineer

28. Sencha Test Page Object
• Clean separation between test code and component locators
• Single repository for the components on the page
• Improve long term maintainability
Developer
QA Engineer

29. External libraries
• Use any NodeJS module or JS library
• Add a library to the “libs” folder and require it in test code
- connect to DB
- connect to Excel
- perform web service call
- etc.
Developer
QA Engineer

30. Local Archive Server
• No need to setup CI process
• No need to use command line
• Store and analyze manual test runs locally
DevOps Engineer

31. ALM Integration
• Publish bugs directly to the JIRA project
• Ignore false negatives
• Review the latest bug status
QA Engineer

32. Sencha Test 2.2 features

33. DOM Tree in Inspector
• Identify Ext JS components and DOM elements
• Use DOM element when component property in unavailable
Developer
QA Engineer

34. Tests Code Visualization
• Tree view for tests
• Generate new tests, indicate asynchronous tests, set pre- and post-
conditions using UI elements
QA Engineer

35. Support for ExtReact
• Full support for testing ExtReact applications
• Use Inspector to find stable and meaningful locators and generate Page
Objects
Developer
QA Engineer

36. Sencha Test
http://sencha.com/products/test/

37. Demo