cakephp-swagger-bake VS testfixtures

I do work in that space. I build APIs and I use them. I built a springdoc for php so I know a bit about what I am talking about: https://github.com/cnizzardini/cakephp-swagger-bake

The Postman UX is not good on it. It's easy to get lost in tabs, they should ditch the tabs and categorize requests under the actual endpoint. There is also no way to easily save like requests and give them better names that is also searchable. It's also built on electron which means its slow and clunky.

There is nothing good in this space. Swagger would do it if they let you save requests to local browser storage and just added a history dropdown to the endpoints. I use swagger and save common requests to a file system and open them in sublime. if its just JSON payloads I am working with it does the job.

This https://github.com/cnizzardini/cakephp-swagger-bake and this https://mixerapi.com have been the result of my work.

This can easily integrate into your existing github actions, here is an example of its usage on a project I maintain: https://github.com/cnizzardini/cakephp-swagger-bake

https://github.com/cnizzardini/cakephp-swagger-bake which builds out openapi from your cakephp applications meta data. One of many projects I took up to occupy myself during covid lockdowns.

Really anything modern works. I thought Laravel was supposed to be easy to learn, but I have only poked around. Symfony is fine, I've done a lot in it. I've used CakePHP a ton and as a shameless promotion I built this OpenAPI/Swagger/Redoc generator for it: https://github.com/cnizzardini/cakephp-swagger-bake/ and if my side project was further a long I'd of course recommend: https://mixerapi.com buts its still alpha.

I'm the author of https://github.com/go-testfixtures/testfixtures, a library written to make it easier to write tests with a real database and test data. You might want to use it together with docker-compose, for example.

To solve the problem we will use testfixtures. Create a folders fixtures и fixtures/storage and put a file users.yaml inside:

A lot of good suggestions here, I would also take a look at go-testfixtures which allows you to create some simple yaml-based fixture data to use with unit testing. It's quick and easy, but yes can get unwieldy the more you add.

I built an alternative to Make written in Go that is simpler to use and cross-platform: https://taskfile.dev/

Also, a library to write tests with databases for Go: https://github.com/go-testfixtures/testfixtures