Ask HN: Microservices testing best practises?
📰 Hacker News · surprised_dev
Learn best practices for testing microservices, including using client libraries, integration testing, and automating tests with Docker
Action Steps
- Create client libraries for each microservice to simplify testing
- Implement integration testing using Docker to automate tests
- Update build environment to support Docker
- Use endpoints instead of mocks for integration testing
- Automate testing to detect changes in dependent services
Who Needs to Know This
Developers, architects, and tech leads can benefit from this knowledge to improve the testing of their microservices-based systems
Key Insight
💡 Using client libraries and automating integration tests with Docker can help detect changes in dependent services
Share This
🚀 Improve microservices testing with client libraries, integration testing, and Docker automation
Full Article
Hello fellow developers, architects, tech leads, Two years ago In my current company we started migration into microservices. The whole project happen without any plan in place. microservices were created ad-hoc, when someone wanted to create something new or just migrated a part of monolith API. We end up having around 15 coupled services. The problem we are facing now are the tests. As we don't have client libraries - project were e.g. User microService is implemented, mock its methods during unit/functional test. Mocks are part of the project consuming this service. Integration tests are done manually on staging. Because of that if something in the given microservices changes we are unable to detect the problem (unless someone spots it on staging). It happens often as developers do not update mocks in depended projects. In future we will run integration testing in docker using endpoints not mock but first we have to migrate our build environment to support docker. Few ques
DeepCamp AI