CodeX
Published in

CodeX

Stop testing your (de)serializers

One of the goals of automated testing is “testing as a safety net” but that doesn’t mean that you should unit test everything. (De)serialization is an example of something that you should not test directly.

According to the hexagonal architecture, an adapter belongs to the outer layer of your app; it’s the glue between a component and the outside world, whether a database, a gateway for a REST API, your own REST API, etc. Adapters should…

--

--

--

Everything connected with Tech & Code. Follow to join our 900K+ monthly readers

Recommended from Medium

Automation with ansible along with industry use cases:

Top 7 Game Development Programs for Beginners

Frontend, Backend, Fullstack: Everything you need to know

light controlling bot

Reli3f nft project collects $1M for Ukraine in 30 secs.

Reli3f nft project collects $1M for Ukraine in 30 secs.

Spark Structured Streaming — Part 1

Optimizing App Start (or any) Time using Video Analyzing Tools

Elixir Concurrent Testing Architecture

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Luís Soares

Luís Soares

I write about Lean, TDD, CI/CD, trunk-based dev., user-centric dev, DDD, coding good practices, testing

More from Medium

Architeture Patterns: Cacing (Part 2)

Pragmatic error handling

Command and Query Responsibility Segregation (CQRS) Architecture

Patterns of Enterprise Application Architecture — Organizing Domain Logic