instaunit VS burp

Shameless plug: for REST APIs, I've written a tool called Instaunit which combines HTTP API integration tests with documentation generation, since these two things must always be maintained in lockstep.

It's got a ways to go before it generates output that looks as good as Stripe's documentation, but it makes it dead simple to create API documentation that's guaranteed to be in sync with your service, because it was generated by your tests when they ran.

https://github.com/instaunit/instaunit

Check out https://github.com/instaunit/instaunit. It lets you define the calls to be made and expected responses and will compare them semantically so you can match on expected fields without worrying about things like dates and IDs that you can't predict easily. It can also be used to generate documentation for your APIs which is awesome because your docs are then built from your tests so you know they are current and accurate.

I tried to give it a different flavor with my demo project: https://github.com/audrenbdb/burp

I posted previously my example repo where I follow Ben's advices, I'll post it again if you want to take a look : https://github.com/audrenbdb/burp

I do that a lot in my example project about clean architecture. See : https://github.com/audrenbdb/burp/blob/main/handle/http/middleware.go

I made a specific repo example of a clean architecture with flat structure here : https://github.com/audrenbdb/burp