TestCorner#22 - Evolving QA implementation for Microservices in Viveport
0 likes141 views
Test corner #22 -Introduction -Issues for deploying service for integration test with Microservices -Service deployment strategy -Docker compose -Docker swarm -Kubernetes (K8s) -Doing BE integration test by each SDET for different service -CI Flow in QA -Q&A
TestCorner#22 - Evolving QA implementation for Microservices in Viveport
- 1. Evolving QA implementation for Microservices in Viveport Laybow Kuo Tech. Manager
- 2. Agenda Introduction Issues for deploying service for integration test with Microservices Service deployment strategy Docker compose Docker swarm Kubernetes (K8s) Doing BE integration test by each SDET for different service CI Flow in QA Q&A
- 3. About me Laybow Kuo Experience Dev / SDET Viveport SDET All Back-End integration test Development of Testing framework Design and Implement for CI/CD flow in QA env
- 4. Microservices + Docker Container Docker container is best presentation for Microservices Viveport has 300 containers
- 5. Viveport Environment Dev QA StageProduction Operation SDET Automatedregression test Continuous Integration environment CI Integration test (BE and E2E) Development and Test Integration
- 6. Issues for deploying service for integration test with Microservices
- 7. Issues for deploying service for integration test How fast you deploy ! Image path and environment value you get Implement docker-compose yaml file (not familiar with syntax or context) How quickly you debug ! Service dependency Environment value DB connection issue
- 10. SG SG SG payment consumer content IP: 10.111.222.1 IP: 10.111.222.2 IP: 10.111.222.3 App record Review record Downloadrecord SG Alipay Credit card Paypal wallet subscription cms
- 11. Issues for docker-compose strategy Memory issue Overwrite sg config Handle component linking issue (not in same docker network) Too many test target Docker Swarm Docker orchestration Overlay network Easy to use / install
- 12. Deployment Strategy: docker swarm $ docker swarm init $ docker network create test_swarm --driver overlay $ docker stack deploy --c xxx.yml --with-registry-auth
- 13. Worker node Master node Worker node IP: 10.111.222.1 IP: 10.111.222.2 IP: 10.111.222.3 App record Review record SG Alipay Credit card Paypal wallet subscription cms
- 14. Issues for docker swarm strategy DNS issue Resource control / Stability Maintain two compose files (compose / swarm format) Docker orchestration Stability Google support
- 15. Deployment Strategy: K8s $ kubectl create f xxx.yml $ kubeclt get pod
- 16. Worker node Master node Worker node IP: 10.111.222.1 IP: 10.111.222.2 IP: 10.111.222.3 Paypal Pod service Alipay Pod service Cms Pod service SG Pod service
- 17. What k8s can help ? Fix memory issue DNS issue Centralized test entry Launch large numbers of container (Stability)
- 18. How to do integration test by each sdet
- 19. How to integration test by each sdet Ansible deploy for k8s infrastructure Each sdet own its QA env Sdet A Sdet B Sdet C QA IntegrationEnv Service B Service A Service C
- 20. CI/CD flow in QA env
- 21. CI Integration
- 22. CI Flow Dev SQS
- 23. 23 THANK YOU Q&A