When it comes to test automation of web application, most of the testers think about Selenium and front end tests. If we are using only Selenium for testing whole functionality, we might end up with enormous number of flaky tests that are hard to maintain, and last way too long. My workshop is directed to anyone interested in gaining knowledge how to write fast and reliable tests in Java using Rest-assured library. I would like to shortly explain, why it is important to limit front end tests, and ensure that critical functionality is covered without clicking through the browser. Most of the workshop will be in the form of practical exercises with code, that will be run against a real application. It will be “bring your own laptop” workshop. Basic Java knowledge required. Tested app will be provided via url or virtual machine. Skeleton of test framework and instruction how to prepare working environment will be provided on github. Topics covered: Rest assured overview. Handling authentication Handling requests. Handling response data. Using response data in requests. Using json body in requests. Creating end2end scenarios. Using Rest-assured as setup for UI tests Exact coverage will depend on group progress during workshop.

1. Quick start to Rest Assured
Szymon Ramczykowski
Lead Test Engineer/Workday Smart

2. Agenda
11/01/2018 2
1. Context
2. Authentication
3. GET Request
4. POST Request
5. PUT Request
6. END2END Scenarios
7. Summary

3. Rest Assured vs Selenium
11/01/2018 3

4. HTTP REQUESTS
11/01/2018 4
Client Server

5. GET/POST/PUT/DELETE
11/01/2018 5
Client Server

6. Resources/Endpoints
Examples
11/01/2018 6
GET https://sampleurl.fake/customers
POST https://sampleurl.fake/customer?name=Steve&surname=Doe
PUT https://sampleurl.fake/customer
DELETE https://sampleurl.fake/customer?id=983987as2

7. RestAssured
11/01/2018 7
http://rest-assured.io/

8. Tested application
11/01/2018 8
https://trello.com
https://developers.trello.com/v1.0/reference

9. Authentication
11/01/2018 9

10. Authentication
11/01/2018 10
VS https://trello.com/app-key

11. Authentication
Reuse authenticate method in specification
11/01/2018 11

12. Authentication
Summary
11/01/2018 12
Trello:
1. User name and password authentication
2. Key and token authentication
Other apps
1. Cookies
2. Tokens
3. Many more

13. GET
11/01/2018 13
1. View board data
2. View cards for given boards
3. View list for given boards

14. GET
Exercise 1- display board
11/01/2018 14

15. GET
Exercise 1- add authentication and endpoint
11/01/2018 15

16. GET
Exercise 1- add authentication and endpoint
11/01/2018 16

17. GET
Exercise 1- test method with pretty print
11/01/2018 17

18. GET
Exercise 1- display board id
11/01/2018 18

19. GET
Exercise 1- display board id
11/01/2018 19

20. GET
Exercise 1- display board id
11/01/2018 20

21. GET
Exercise 1- display board id
11/01/2018 21

22. GET
Exercise 2- display cards
11/01/2018 22

23. GET
Exercise 2- using getBoardId as parameter
11/01/2018 23

24. GET
Exercise 2- get card id
11/01/2018 24

25. GET
Exercise 2- get card id
11/01/2018 25

26. GET
Exercise 2- testing methods
11/01/2018 26

27. GET
Exercise 3- list display
11/01/2018 27
Endpoint: /boards/boardId/lists
1. Display list method
2. Display list id
3. Test both methods

28. GET
Summary
11/01/2018 28
1. Reuse of specification
2. Response object/Json mapping
3. Get items id: boards, cards, lists

29. POST
11/01/2018 29
1. Create new board
2. Create card on new board
3. Create list on new board

30. POST
Exercise 1 create board
11/01/2018 30
Endpoint: /boards/
1) Handle authentication
2) Add parameter: queryParam(“name”, ”Your
board name”);

31. POST
Exercise 2 create card
11/01/2018 31
Endpoint: /cards/
1) Handle authentication
2) Add parameter: queryParam(“name”, ”Your
card name”);
3) Add parameter: queryParam(“idList”, “Your
list id); //reuse getId method from
GetRequests class.

32. POST
Exercise 3 create list
11/01/2018 32
Endpoint: /lists/
1) Handle authentication
2) Use trello documentation to find out what
parameters you need to add new list
https://developers.trello.com/v1.0/reference

33. POST
Summary
11/01/2018 33
1) Authentication
2) Reuse of get methods
3) Created new board, card list

34. PUT
Exercises
11/01/2018 34
1) Change card name
2) Move card to other list
3) User trello documentation to get
parameters and endpoints
4) Reuse getId methods where appropriate

35. PUT
Summary
11/01/2018 35
1) Used documentation of trello.
2) Reused getId methods.

36. END2END testing
11/01/2018 36
1. Create new board with unique name
2. Create 4 cards on new board
3. Create new list on new board
4. Rename one of the cards
5. Move one of the cards to list Doing
6. Move other card to list Done
7. Move other card to new list

37. Summary
11/01/2018 37
What we did:
- Covered 7 Endpoints
- GET(Board, Card, List)
- POST(Board, Card, List)
- PUT(Cards)
- Different aspects of authentication
- Using of documentation
- Using network tab
- Response handling
- End 2 end testing with methods reuse.

38. Summary
11/01/2018 38
What we could do:
- Start flow from post request
- Cast json data to java classes
- Data clean up
- Better structure of project

39. Summary
11/01/2018 39
What you can do:
- Experiment with examples, enhance those, add
parametrization, add other test cases
- Experiment with other apps
- Jira
- Facebook
- Twitter
- Your company app
- Learn other tools: Postman, SoapUI, JMeter, Gatling
Code with answers available in repo:
https://github.com/szmc/aadays-restassured-workshops

40. Questions?
11/01/2018 40

41. Thank you!
11/01/2018 41