alex-freire

5 ms·

1. 1.▲
   by alex-freire 5y ago

   you’re right sir!
2. 2.▲
   by alex-freire 5y ago

   well put! thanks for the great summary.
3. 3.▲
   by alex-freire 5y ago

   thank you
4. 4.▲
   by alex-freire 5y ago

   sorry for the bait. thanks for the click :-D
5. 5.▲
   by alex-freire 5y ago

   that's a very good alternative way of thinking about E2E
6. 6.▲
   by alex-freire 5y ago

   exactly! well said. it's what we're trying to achieve with our acceptance testing strategy. you can see more here how we leveraged clojure to be able to simulate E2E in memory in the JVM by bypassing IO and just having one service
7. 7.▲
   by alex-freire 5y ago

   well said!
8. 8.▲
   by alex-freire 5y ago

   we didn't see more bugs in production when we sunseted E2E. in fact, complementing contract tests with acceptance tests we saw less bugs in production and more productive test creation and maintanence. :-D
9. 9.▲
   by alex-freire 5y ago

   And in part 2 about 12 minutes in we show the code to exemplify how our acceptance test suite works (and is very different from traditional E2E): https://www.youtube.com/watch?v=caxpxszueI0&list=PLfqo9_UMdH...
10. 10.▲
    by alex-freire 5y ago

    Thanks for the feedback, we didn't want to burry the "acceptance test" complement to our testing strategy in the article. If you're curious how it works we've recorded a webinar about it: https://www.yout