Learn how you can improve the quality of web applications through Sencha Test 2.2. We’ll demonstrate how you can build robust tests using Page Objects, visualize tests using a tree view and utilize unique locators by using the DOM Tree directly from Sencha Studio.
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
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
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
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