Part 2 of our point of view on microservices service testing. Overview of how Mesh Dynamics API Studio can be used for testing services in isolation -- either pre-submit or in CI.
https://t.co/haaaX8B1ed
Part 1 of our point of view on microservices service testing. We take a look at three test types associated with microservices APIs, and explain them from our perspective. https://t.co/oed6DBGo3j
Mocks play in enabling service testing for microservices applications. @VenkyGanti describes how Mesh Dynamics is making it easy to scale mock creation and service testing.
https://t.co/C96HBWNToa
Testing each service with its producers and consumers early helps detect functional (including integration) issues early. @VenkyGanti outlines how Mesh Dynamics leverages API tracing to speed microservices API testing and debugging.
https://t.co/YEbj4vXpmH
Different types of tests for microservices applications: Reality does not follow the idealized microservices testing pyramid. This is our take on the current reality based on customer conversations. https://t.co/3xmsoHfKbJ
@VenkyGanti looks at the role mocks play in enabling service testing for microservices applications, and how Mesh Dynamics is making it easy to scale mock creation and service testing.
https://t.co/C96HBWNToa
Service testing should help the velocity of microservices application development by enabling independent deployment of services. In practice, the process is not so simple to adopt. @nmani1978 talks about the practical challenges in this article.
https://t.co/ShyAnobBZh
Service testing is essential to microservices applications. Here we explore why you need service testing, and some of the challenges involved. https://t.co/djUk6pHwWv
Short article by Venky Ganti based on our learnings about common development practices eng teams are using for microservices development.
https://t.co/2e4zNIcJ9R
The third and final part of the series by
@nmani1978 about considerations for choosing the right dev environment for microservices development. Part 3/3
https://t.co/dLRcGmCYIU
The second part of the series by @nmani1978 about considerations for choosing the right dev environment for microservices development. Part 2/3
https://t.co/q3WPxjJTEj
#Microservices adoption is on the rise, and there are lots of reasons to adopt microservices architecture. @nmani1978 discusses the considerations for choosing the right environment for microservices development. https://t.co/aa7CrKTt5h
“Don’t mock types you don’t own” per #Google’s #testing blog https://t.co/EXJqCQpI8B. Especially true for #microservices. Services mock requests and responses of related services! Keeping these mocks in sync with reality is a nightmare and bugs only found in #integrationtesting.
Variety of reasons to adopt #microservices and variety of challenges. The least talked about is the massive amount of eng effort for creating automated #testing and #debugging https://t.co/sHVCLoEtsY
#continuous#testing critical for Shift-left even if delivery is periodic. Needs lot of discipline to implement since #engineering effort needed to achieve even reasonable automation coverage is massive.
Testing is the heart of DevOps. You cannot do continuous delivery without continuous testing. - @lisacrispin & @janetgregoryca (shoutout to @aahunsberger) #EuroTestConf