Download to read offline
Uploaded byRoy Braam
End-to-End test architectures, a dead End road
The document outlines the challenges and architecture of end-to-end (E2E) test environments, emphasizing the need for production-like settings to ensure effective testing. It discusses issues such as trust in automated testing, data management, and the complexities of deploying in various environments. The document also touches on the migration to public cloud platforms and highlights the use of consumer-driven contract (CDC) tests to minimize risks and improve quality assurance.
More Related Content
![Smarter testing and never waste time again [Workshop]](https://cdn.slidesharecdn.com/ss_thumbnails/smarttestingworkshop-170929095301-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to End-to-End test architectures, a dead End road
End-to-End test architectures, a dead End road
- 1. End-to-End test environments 11/7/2019 RoyBraam @rbraam
- 4. End-to-End test environments 11/7/2019 RoyBraam @rbraam
- 21. Roy Braam @rbraam11/7/2019 End-to-End testenvironments
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30. Public Cloud Node NodeNode ControllerManager API
- 31.
- 32.
- 34.
- 35. End 2 Endtest environments
- 36. The End-to-End testenvironment
- 37. “A complete integrated environmentwith production like systems, with the single purpose of testing”
- 38.
- 39.
- 40. The dead endroad
- 41.
- 42.
- 43.
- 44. Not so “productionlike” Version: Production Version: Production Version: Production Version: Production Version: Production Version: Production Version: Production+1 Version: Production+1 Version: Production+1 Version: Production-1 Version: Production+1 Version: Production-2 Version: Production-3 Version: Production-4 Version: Production+2
- 45.
- 46.
- 47.
- 49.
- 50.
- 51.
- 52.
- 53.
- 55. Dev: Hey, canyou help me out. Our flow is not working on the environment 3, can you have a look if the platform is the cause Dev: Yes.... Hey, now it's working. O, wait. You are looking at environment 3 small. Me: Sure. I don't see any problem with the platform. Can you show me the broken flow on my device? Support conversation to a team
- 56. Me: Yes, thatis what you said, environment 3... Dev: No, I meant environment 3 big Me: But that's the same platform, it's environment 3. Dev: No, it is a small environment 3 Me: But it connects to the same services for us. Dev: But not to us, in environment 3 small we connect to services in environment 5 big Me: What !!?!?
- 59. Migrating Platform tothe public Cloud End-to-End Environment
- 60.
- 61.
- 62.
- 63. “Tests with semanticcorrect data can only be run in a End-2-End test environment.”
- 65.
- 66.
- 67. “I want tosee it work before I go to production”
- 68. What I hear: “Idon't trust the automated tests we implemented.”
- 69. Or: “We don't haveautomated integration tests, we like manual testing labor”
- 70. What if youdon't “Talk the Talk, Click the Click”?
- 71.
- 72.
- 73. “System X hada new release that broke our system, even though the contract is the same.”
- 74.
- 75.
- 76. “When they releasea new version we first want to test our system, they often break things.”
- 77.
- 78.
- 79. “Our stakeholders demandthat we first show it in an End-2-End environment, with that we guarantee our quality”
- 80.
- 81.
- 82.
- 83.
- 85.
- 86. Reveal Unused Interfaces Well-Fittedness Costs Stability Feedbacktime - - - - - - + - - - + + + + + + + Maintenance Effort +- + Complexity Test Data Setup Testing Data Semantics +- - + + + E2E Tests CDC TestsMock Tests Isolation +- + + https://reflectoring.io/7-reasons-for-consumer-driven-contracts/
- 87.
- 88.
- 89.
- 90. Canary release Router /Load balancer Version N Version N+1 99 % 1 %
- 91. Blue/Green deployments Router /Load balancer Blue Green production.example.com production.example.com test.example.com
- 94. 11/7/2019 Roy Braam@rbraam
- 95.