The idea is to show more complex test automation architecture which goes beyond the ordinary arrange->act->assert or set-up->run tests->tear-down workflow.

1. Test automation architecture.
Advanced level
Anton Skomarovskyi
22 February, 2019

2. Anton Skomarovskyi
Engineer with more than 6 years in IT
• Senior QA Automation Engineer at CloudMade
• www.linkedin.com/in/anton-skomarovskyi
• Was working at:

3. Agenda
• Warming up. Good & Bad examples
• CloudMade product presentation and setting test requirements
• Introduction into MapReduce Jobs’ topic
• Test Automation Framework and its architecture
• Results and plans for future
• Q&A

4. Integration tests
How should NOT be done
Example #1

6. Let’s
make it better

8. Example #2
Set up
Prerequisite works
to be done
Act
Source of testing
Tests
Running test cases
REST API

10. CloudMade
connects the dots on every human journey

11. Smart
Onboarding
Personalized Autonomy
Predictive Navigation
Personalized Search
Predictive Call List
Personalized Coaching
Intelligent Cabin
Intelligent
Climate
Refueling and
Recharging
One Driver
Profile
Many Use Cases
Personalized
Parking Options
Predictive
Drive Mode
Predictive Media
Predictive
Occupant ID

12. Distributed Computing
• Hadoop MapReduce
• Apache Spark

13. val mySeq: Seq[Int] = 1 .. 99
val mySeq_1 =
1 .. 33
val mySeq_3 =
67 .. 99
val mySeq_2 = 34 .. 66
Example

14. val result: Int = 4950
561
1650
2739
val mySeq_1 =
1 .. 33
val mySeq_3 =
67 .. 99
val mySeq_2 = 34 .. 66
Example

15. Server-side
architecture

16. Client
SDK
HBase
Events
2. MR Job
Extract Journey
Journeys
3. MR Jobs
Inderence Engine
PosgreSQL
Inferences
Users
Predictions
4. API
Fetch new Profile
1. Upload Data
Raw events

17. Test requirements
• Test MR Jobs’ logic
• Test REST APIs
• Run MR jobs
• Import test dumps to DB

18. The First attempt

19. Simple solution
• All in one. Tests are responsible for:
1. Import test dumps to DB
2. Run MR jobs
3. Test MR Jobs’ logic

20. What’s Jenkins Pipeline?

21. Steps:
Jenkins Pipeline
1 2 3 4 5

22. What’s the Problem ?

23. Tons of logs

24. Not clear what time it is
Test run ? MR Job run ? Import dump to DB ?

25. Solution problems:
• No transparency in understanding what is
currently running
• Hard to understand what is failed
• No opportunity to see the trends of different
component runs in the past

26. Wait…
How about making
Revisions?

27. Modularity

28. Updated requirements
• Modularity (Jenkins Pipeline via Steps)
1. Test MR Jobs’ logic
2. Test REST APIs
3. Run MR jobs
4. Import test dumps to DB
• Configurable run via Steps

29. Let’s make the
Second attempt

30. Use case

31. Architecture
solution

33. Files hierarchy

34. Director [Entry point]

35. How to run the solution?
$ java -jar app.jar --help

36. Jenkins’ pipeline [code]

37. Transparency
Jenkins’ pipeline

38. Conclusion

39. Transparenc
y
Modular solution
Configurable
Via Steps
Flexible
To Change

40. Anton.Skomarovskyi@gmail.com
Thank you!