>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3541338. --> Reported by: [yautja_cetanu](https://www.drupal.org/user/626050) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The tests themselves are varied and valuable. There are many different types of conversations people could have and many different things the Agents could do. It would be great if we could significantly speed up the creation of test collections, test groups and tests and make it so the community can easily submit them without too much time taken with the community.</p> <p>Things we need to think about:</p> <ul> <li>Where do we want to store these tests? Can we put them on github? Should we make a website dedicated to this task? Can we make it so people can submit tests without too much admin approval?</li> <li>Can we then build something similar to project browser that allows you to search and find tests to bring in and make use of. (Could even make use of project browser itself as another source?)</li> <li>People should be able to submit the tests, with test collections and test groups and any Recipies or configuration needed to be applied before the tests run.</li> <li>The tests will need to report on the version information that is required vs version information that was used to create the tests.</li> <li>People should be able to submit some results alongside the tests for specific models. Test results that have high quality results can then be used as training data to train open source models. Though we don't necessarily need to import the results.</li> <li> We will need things like what Agents from what Modules these are testing. It could include Agents in the recipe if they are custom agents. In fact maybe all submitted tests always come with something like a composer.json file to mention the initial setup of the test?</li> </ul> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3> > Related issue: [Issue #3560677](https://www.drupal.org/node/3560677)