Thought ultimately this would be a key aspect of delivering intelligence applications. The architectural design and selection of what each service looked like, and how they can be implemented to interact. A reminder of our look at Object Oriented programming, This is only the start to make things workable, and most important: maintainable.
Architecturally Aligned Testing
By Stefan Friese in InfoQ
, reviewed by Shane Hastie
Key Takeaways
Microservices are typically owned by cross-functional and autonomous teams, responsible for implementing, testing, and releasing.
When implementing a microservices architecture there should be no separate testing phase.
Everybody is responsible for the quality of the product.The complexity of integrating microservices requires carefully deciding the appropriate integration test approach.
Continuous Testing means a shift left in testing to ensure that teams stay autonomous and a shift right in testing towards exploration and experimentation. ...
Architecture impacts heavily testing. The way you test a monolith is different than how you should test a loosely coupled system. Let’s look at microservices as a prominent exponent of loosely coupled systems. As we will see, they challenge our previous definition of testing.... "
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment