Jo presented on the challenges of testing micro-services at VIVEPORT and their solution. VIVEPORT uses over 300 micro-services that require function, integration, end-to-end, performance, and production monitoring testing. Some of the challenges included inconsistent business logic, requirement changes impacting schedules, and the effort of regression testing. To address these, VIVEPORT implemented a process where product owners define test plans, developers implement features and prepare tests, and SDETs execute and review tests. This aligned teams, improved quality, and reduced testing effort so that all features could be tested.

1. Path to survive among
micro-services for QA
Jo
Sr. Manager

2. Jo Du
• VIVEPORT Testing Head
• Experience: Application Developer
Yahoo Automation QA
HTC Cloud Service SDET

3. Agenda
• Introduction of VIVEPORT
• SDET Role
• The challenge we met
• How to!
• Achievement
• Q&A

4. Introduction of VIVEPORT

5. Backend Services

6. Roles Composition
Marketing
Product Owner
Designer
Operation
Engineering

7. Roles Composition
Product Owner
Designer
Project Manager
Developer
Customer Support
SDET

9. About 300 micro-services

10. SDET Role

11. Function Test of all micro-services
- Python
- Scala
Automation Framework
Viveport
FE
Store
Entrance
Payment
Entrance
Enterprise
FE
Microservice 2Microservice 1
Microservice 3 Microservice 4
Microservice 6Microservice 5

12. Integration Test of all entrances
- Python
- Scala
Automation Framework
Viveport
FE
Store
Entrance
Payment
Entrance
Enterprise
FE
Microservice 2Microservice 1
Microservice 3 Microservice 4
Microservice 6Microservice 5

13. End to End Test
- Viveport-Web
- Viveport-Desktop
- Developer Console
- Arcade
- Enterprise
- Internal Tool
E2E Clients
Viveport
FE
Store
Entrance
Payment
Entrance
Enterprise
FE
Microservice 2Microservice 1
Microservice 3 Microservice 4
Microservice 6Microservice 5

14. Performance Test
Target
Evaluation
Test
Plan
Automation
Script
Stress Test
Longevity Test
Performance
Test Report

15. CI Integration

16. Production Monitor

17. The challenge we met

18. Business Logic inconsistent
Requirement Change and Schedule ImpactLimitation of Integration Test
Micro
service
3rd Party
Mock Server
DB
Connection
Effort of Regression Test
New
Previous

19. How To !

20. Submit
User Story
Product Owner
conduct a kick-off meeting
(communicate business goal)
PGM
define
Feature Test
RD/SDET
implement
Features
RD
prepare test
Function/Integration/E2E
SDET
review
Entry Criteria
RD/SDET
execute test
Function/Integration/E2E
SDET
Architect
Design
Service Spec
RD
- Pass feature test coverage rate
- Pass feature test logic review
- Pass regression test
Entry Criteria
Review
Design
Arch/PGM/RD/SDET/OPS

22. Achievement

23. • Down-to-earth
• Alignment
• Quality
• Efficiency
• Reduce effort
• All feature can be tested

25. Q&A