11 Comments

Great article!, Daniel.

In the past, I had a bug that took me days to reproduce, and it finally only occurred when the entire scope was used.

Since then, I do end-to-end tests for happy paths using Superset with a staging or in-memory database.

I use sociable tests starting from the controllers, testing the cases more exhaustively and mocking the data layer with test doubles.

Regards

Expand full comment
author

This is the way, glad to hear that Jorge! Keep rocking it!

And thanks!

Expand full comment

Great article to understand the difference between solitary and sociable tests.

Expand full comment
author

Thank you Gina!

Expand full comment

Web APIs are social interfaces; we should prioritize Sociable Tests.

Especially on critical paths, like order processing or user registration workflows, often require the highest confidence, and your test suite should closely mirror production behavior.

Simply put, Daniel!

Expand full comment
author

Social interfaces requires sociable tests. Love this, thanks brother!

Expand full comment

Another fantastic article my friend Daniel!

Learned something new today

Expand full comment
author

Thank you my friend!

Expand full comment

Sociable unit tests are great because they express behavioral outcomes and they are stable when refactoring. As you said, I, too, go down to Solitary unit tests when needed - generally when I need to write more complex implementation and/or combinatorial explosion, as Ian Cooper says "shifting gears".

Expand full comment

EchoAPI offers all the essential features I need for effective API testing, from authentication to detailed request management.

Expand full comment

We had to work with multiple APIs for user authentication, posting content, handling comments, and managing reactions. EchoAPI made the testing process incredibly efficient, ensuring that every feature worked seamlessly in real-time.

Expand full comment