Coce needs more comprehensive tests

[tomascohen]

We are seeing some crashes in production, they are related to the lack of try/catch blocks in some places. This behavior should have mocked tests to cover it.

I'm gonna give it a try.

[tomascohen]

I'm gonna use some AI to speed things up and also to cover as much as possible from their specs.

[fredericd]

Just seeing your full_refactor branch => insane quality, and comprehensive work! Tell me if I can help, or what you need, or what you see as the next step.

[tomascohen]

I think Coce deserves a v2.0.0 for the revamp, but maybe we need to work on the README a bit. Having a ## PM2 deployment section, and a ## Docker one.

We need testers for the sample compose file and eventually adjust it to 'just work' if that wasn't the case.

In my deployment I'm using the traefik reverse proxy. And example configuration could be added for this use case too.

I think we need to move forward and get the ball rolling.

[fredericd]

100% agree. I'm finishing tomorrow a trek around Briançon, afterward I will push you PR. I'd be very interested to learn your journey with IA (and your brain) in order to track down bugs, improve drastically testing coverage, and more...

[jaideraf]

@tomascohen not exactly related to this issue, but I am curious about what you think on these subjects: #17 and #16

Maybe you could integrate your changes and make tests to these cases, too.

[tomascohen]

We definitely want regression tests for those. I think they should be worked on in their own reports. I'm closing this one.