Testing Microservices, the sane way – Cindy Sridharan – Medium


90 bookmarks. First posted by bjartek 18 days ago.


But also - massive integration tests spanning every possible service our service interacts with isn't scalable either. It's slow by default - and integration tests only yield full value when the feedback is *fast*. We need a better template to test distributed systems.
microservice  testing 
8 days ago by clehene
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and not desktop software or safety critical systems or GUI tools or frontend applications and what have you.
Distributed systems means different things to different people.
For the purpose of this post, by “distributed system” I mean a system composed of many moving parts, each with different guarantees and failure modes which, together, work in unison to provide a business feature. This certainly isn’t close to the canonical definition of a “distributed system”, but these are the kind of systems I have most experience working with and I’d argue these are the kind of systems the vast majority of us build and operate. Albeit we’re talking about a distributed system, the terminology du jour is “microservices architecture”.
microservices  Testing 
8 days ago by cnk
Yep! The whole point of microservices is to enable teams to develop, deploy and scale independently. Yet when it comes to testing, we insist on testing *everything* together by spinning up *identical* environments, contradicting the mainspring of why we even do microservices. https://t.co/Z9tzeOkIvQ
microservices  testing  distributedsystems 
8 days ago by harald
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and not desktop software or safety critical systems or GUI tools or frontend applications and what have you.
microservice  testing 
9 days ago by danesparza
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
12 days ago by leeomara
Testing Microservices, the sane way – Cindy Sridharan – Medium
from twitter_favs
13 days ago by philcrissman
Post by - 39 minute read and then 3 days to keep processing it in your head.
from twitter_favs
13 days ago by wschenk
Must read !!!!!!!
microservices  testing 
14 days ago by hayzer
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
15 days ago by scubaninja
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and not desktop software or safety critical…
testing  Microservices 
15 days ago by spdaly
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
15 days ago by aburgel
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
16 days ago by bkeetman
If there’s anything I’ve learned in the last few years of witnessing how services fail, it’s that pre-production testing is a best effort verification of a small subset of the guarantees of a system and often can prove to be grossly insufficient for long running systems with protean traffic patterns.
testing-in-production 
16 days ago by foodbaby
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
16 days ago by dylan
Yep! The whole point of microservices is to enable teams to develop, deploy and scale independently. Yet when it comes to testing, we insist on testing *everything* together by spinning up *identical* environments, contradicting the mainspring of why we even do microservices. https://t.co/Z9tzeOkIvQ
testing  microservices 
16 days ago by geetarista
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and not desktop software or safety critical systems or GUI tools or frontend applications or what have you. via Pocket
16 days ago by goeran
think about this in terms of stacks/dev setup at work
testing  microservice 
16 days ago by jessedavis
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
16 days ago by granth
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
16 days ago by aviflax
I’ve previously written in great detail about “post-production testing” from primarily an Observability standpoint. Monitoring is a form of post-production testing, as is alerting, exploration and dynamic instrumentation. It might not even be stretching it to call techniques like featuring flagging and gating as forms of testing in production. User interaction or user experience measurement — often performed using techniques like A/B testing and real user monitoring — constitute as testing in production as well.
microservice  testing  monitoring  ci  deployment 
16 days ago by euler
Charity is right — these aren’t the sort of things you’d ideally want to be “monitoring”. In the same vein, these aren’t also the things you’d want to be “testing” pre-production. Distributed systems are pathologically unpredictable and it’s impossible to envisage the combinatorial number of quagmires various parts of the system might end up in. The sooner we come to terms with the fact that it’s a fool’s errand to try to predict every possible way in which a service might be exercised and write a regression test case for it, the sooner we’re likely to embrace a less dysfunctional approach to testing.
microservices  quality  Emergence 
16 days ago by janpeuker
@mipsytipsy @ErikSeaberg @colourmeamused_ 1000% Failure gonna happen. Hell, it may not even be something you did. (I'm looking at you S3zure) The reason is not deployment, the reason is Internets. Unless you put your software in a box you work in ops now. Code accordingly.
microservices  testing 
16 days ago by rocha
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
16 days ago by jdelStrother
Testing Microservices the sane way ()
from twitter_favs
16 days ago by hendry
Testing Microservices the sane way: Comments:
from twitter_favs
16 days ago by isaacsu
Testing Microservices the sane way (cmts )
from twitter_favs
16 days ago by rukku
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing backend services and…
from instapaper
17 days ago by indirect
> [...] trying to spin up the full stack on developer laptops is fundamentally the wrong mindset to begin with, [...]. In fact, doing so is tantamount to building a distributed monolith.
microservice  architecture  testing  vagrant  from twitter_favs
17 days ago by floehopper