>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3555753. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !8 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently the testing framework has a custom way of doing export and imports via the GUI, that flattens everything to one file, even complex test groups.</p> <p>There are also Drush commands for importing such a file, when you want to run it in CI (drush agents:test-agents-group-import)</p> <p>However this will cause issues when someone wants to install a test suite via recipes, since recipes assumes that each content part should be its own file. We are also introducing possible file entities in <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/ai_agents_test/-/work_items/3555548" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/ai_agents_test/-/work_items/3555548</a></span>, so they should also be importable, something the recipes support already.</p> <p>From Drupal 11.3 you can use the drupal cli command to do more or less what we describe here, but to make it simpler we should still include this command.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Create a seperate command that is called agents:test-agent-group-recipe-export (agetre).</li> <li>It should take a directory where the recipe should be built, the recipe data name (folder), recipe readable name and which test group to use. All required.</li> <li>The recipe should not exist - if you only want to export the files, you can push it to a tmp directory and copy out the content directory.</li> <li>The command will generate a recipe, that requires AI Agents Test module, that the given agents exists, creates a recipe skeleton and the content.</li> </ul> <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>