This document proposes an automated test architecture for the UI Builder application using REST API testing, UI testing, and integration testing. It recommends the Rest Assured library for API testing due to its ability to integrate with Jenkins and remove the need for manual HTTP calls. Protractor is proposed for UI testing as it allows testing Angular applications in JavaScript and integrates well with Selenium. Both test frameworks would be set up with their own Git repositories linked to Jenkins jobs. Integration testing would link the API and UI test repos. The test automation aims to provide faster feedback and reduce regressions as the application grows.

1. UI Builder
Test Automation
Proposal
Mihai-Cristian Fratila
Software Engineer in Test & Scrum Master
Phoenix team

2. Topics
1. Why we need test automation?
2. Types of tests that we need
3. Test architecture for each type
4. Tools proposal for each type
5. Integrating CI tools & VC systems
6. Demo

3. How it all started?
• Action item from Sprint 18.4 SP1 retrospective

4. Reasons why we need
automated tests
• UI builder app gets bigger by every sprint
• App in early phase -> a lot of regression issues
• Tests performed manually by now
• Automated tests will provide faster feedback while
developing features
• Automated tests should be started while the app is in a
early phase and progress alongside the development
process

5. Examples of regression bugs

6. Level of testing

7. API Testing
• Pros: Cons:
• Allows user to create collections. - cannot integrate with Git
• Allows user to semi-automate tests. - cannot integrate with Jenkins
• Gives feedback quick.
• Allows user to create env variables.
• Allows user to create tests without hardcoding values .

8. DEMO

9. API Testing
• Java library that provides domain specific language for writing powerful and
maintainable REST API tests.
• Pros:
• Removes the need for writing code to set up HTTP connection, send a
request and receive and parse the response
• Supports given/when/then test notation, which make your tests human
readable.
• Since it is a Java library, it can be integrated very well with Jenkins.

10. Framework architecture
Rest Assured Test -
Folders and UI Objects
CRUD operations
Maven
Build automation tool
Test NG
Testing framework and
reporting for Java

11. Tests Architecture
Rest Assured Test -
Folders and UI Objects
CRUD operations

12. Tests Architecture
HTTP helper
methods
Data
payload
Resources
(URLs)
General Utils
Rest Assured Test -
Folders and UI Objects
CRUD operations

13. DEMO

14. Level of testing

15. UI Testing
• e2e testing framework for (Angular) js applications.
• Wrapper around Selenium WebdriverJS and Selenium Server
• Open source, hosted on Github.
• Records tests running in a real browser.
• Interacts with page elements as a real user would.
Alternative: - Selenium Webdriver

16. Why Protractor ?
• Whole development team is using Javascript as main language for frontend -> Protractor is
developed in Javascript.
• Has a lot of new locators strategies and functions. Allows users to create custom locators.
(show example with custom locator for shadow down elements)
• Automatic waiting, can execute the next step in your test, the moment the webpage finishes
pending tasks.
• Can run on both real and headless browsers.
• Can be integrated with CI tools.

17. How it works?
• A test involves 3 processes: the test script, the server and the browser.
• Selenium Server takes care of interpreting commands from the test script and forwards them
to one of the browsers, through WebDriver Wire Protocol interpreted by the browser’s driver.

18. Framework architecture
Npm
package manager for
JavaScript
Jasmine
BDD testing framework
and reporting for JS
Protractor test - e2e flow

19. Tests architecture
Protractor test - e2e flow

20. Tests architecture
Protractor test - e2e flow
jsonData
Page
Objects
Utils
Configuration
file
Package.json

21. DEMO

22. Level of testing

23. Integration
• Each framework to be part of a separate repo on
Git.
• Each repo from Git will be linked to a Jenkins job.
• REST Api tests should be used as a sanity tests.
• UI Tests should be used as regression tests.

24. DEMO

25. What’s next
• Talk to Balaji and propose this test architecture.

26. What’s next?
• Owner of the test process is the entire Phoenix
team.
• We work agile and have full control over the entire
software development process.
• US creation -> PI planning -> Backlog grooming
-> Sprint planning -> Sprint execution
(development & testing) -> Track progress ->
Present report at SOS -> Improve process
(Retrospective)

27. What’s next?
• Keep checking new tools that will help us more:
• newman
• Protractor-image-comparisson
• Analyse integration of Protractor with Typescript

28. Q&A