How was Chiron tested before being publicly released?

[marcelovicentegc]

How was Chiron tested before being publicly released?

Hey, all! This is the first time I write something about the journey of developing @eutiveumsonho. Chiron is intended to be used as a companion service for your own services that need some human-review process of AI generated data. This means that Chiron doesn't do much on its own. It needs to receive data from somewhere, and send its reviewed version back to its origin or even somewhere else. To make sure that Chiron was working as expected, I tried:

Spinning eutiveumsonho locally along with Chiron

Spinning both of these services, that rely on next-auth under the hood, didn't work well. That's because next-auth subscribes all session data to localhost, and since both services were running on localhost, the session got messed up, even if the services were running on different ports. I didn't take time to dive deeper on a possible workaround for this, so I wrote a test server to make sure that the API was ok.

Spinning a test server locally along with Chiron

Since the test server doesn't rely on next-auth, testing Chrion's API is really straight forward. So straight forward that every time you spin up Chiron, the test server is setup and automatically generates a completion and sends it to Chiron. This allowed us to make sure that the API was working as expected, at least locally, and improves the developer experience as well. The next step was to test it in a production environment.

Testing Chiron on a preview environment

We already had a preview environment setup for eutiveumsonho, so we just configured both service's to communicate properly by creating an API key to eutiveumsonho from Chiron's API Management page, and did some changes to eutiveumsonho's workflow to send data to Chiron's pipeline. As of the day that we're writing this (10th of December/2023), it's working like a charm. We will keep testing the integration throughout this week until actually moving it to production to make sure this release goes smooth. Once this is done, we will wait for another week before actually making this project publicly available.

If you want to learn more about the changes made to eutiveumsonho to integrate with Chiron, just take a look at:

• feat: send all completions to chiron pipeline #79