>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3566649. --> Reported by: [fago](https://www.drupal.org/user/16747) >>> <h3 id="summary-problem-motivation">Motivation</h3> <p>Automated tests that proof all features of the provider are working.</p> <p>We want automated tests to mock the mistral API.</p> <p>On top, it would be great to have some simple integration tests that verify compatibility with the real API.</p> <h4 id="summary-steps-reproduce">Analysis</h4> <p>The existing tests of php-mistral require a real Mistral API key via environment variables:</p> <pre>&nbsp; export MISTRAL_API_KEY=your-api-key<br>&nbsp; export MISTRAL_CHAT_MODEL=mistral-large-latest</pre><p>The test coverage of the API clients seems in-complete, here an AI-generated analysis:</p> <table border="1" cellpadding="6" cellspacing="0"> <thead> <tr style="background:#333;color:#fff"> <th>Feature</th> <th>Tested</th> <th>Notes</th> </tr> </thead> <tbody> <tr style="background:#d4edda"> <td>Chat (stream/non-stream)</td> <td>&#9989;</td> <td>Well covered</td> </tr> <tr style="background:#d4edda"> <td>MCP Tools &amp; Prompts</td> <td>&#9989;</td> <td>Extensive</td> </tr> <tr style="background:#d4edda"> <td>Agents</td> <td>&#9989;</td> <td>Via MCP tests</td> </tr> <tr style="background:#d4edda"> <td>Conversations</td> <td>&#9989;</td> <td>Via MCP tests</td> </tr> <tr style="background:#d4edda"> <td>Libraries CRUD</td> <td>&#9989;</td> <td>Full coverage</td> </tr> <tr style="background:#d4edda"> <td>Documents CRUD</td> <td>&#9989;</td> <td>Full coverage</td> </tr> <tr style="background:#f8d7da"> <td>Embeddings</td> <td>&#10060;</td> <td>Not tested</td> </tr> <tr style="background:#f8d7da"> <td>Moderation</td> <td>&#10060;</td> <td>Not tested</td> </tr> <tr style="background:#f8d7da"> <td>Classifications</td> <td>&#10060;</td> <td>Not tested</td> </tr> <tr style="background:#f8d7da"> <td>OCR</td> <td>&#10060;</td> <td>Not tested</td> </tr> <tr style="background:#f8d7da"> <td>FIM (code completion)</td> <td>&#10060;</td> <td>Not tested</td> </tr> <tr style="background:#f8d7da"> <td>File Management</td> <td>&#10060;</td> <td>Not tested</td> </tr> <tr style="background:#f8d7da"> <td>List Models</td> <td>&#10060;</td> <td>Not tested</td> </tr> </tbody> <tfoot> <tr style="background:#eee"> <td><strong>Coverage</strong></td> <td colspan="2"><strong>~50%</strong> &mdash; Core chat/MCP good, embeddings/moderation/OCR missing</td> </tr> </tfoot> </table> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>- Add test-coveraged with mocks. Evaluate and test on the best way to do it. So far AI-providers did do both guzzle middleware, but also <a href="https://mockoon.com/">https://mockoon.com/</a> to setup an actual API response. However, there is also <a href="https://docs.saloon.dev">https://docs.saloon.dev</a> as a popular tool from the laravel universe what might be helpful. (That's used by <a href="https://github.com/HelgeSverre/mistral/tree/main/tests">HelgeSverre/mistral</a>)<br> - Configure running the php-mistral inference tests with a public mistal API key, using its free tier. Configure a scheduled pipeline for it.<br> - Consider submitting upstream PRs to complete test-coverage</p> <p>Let's work in sub-tasks/issues for individual steps!</p>