>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3546760. --> Reported by: [hooroomoo](https://www.drupal.org/user/3688872) Related to !241 >>> <h3 id="overview">Overview</h3> <p>Add a playwright e2e test of the user flow for </p> <p>1. Creating a content template<br> 2. Confirming that the suggestedPreviewEntityId is used as the example content when the template is open<br> 3. Adding a component to the template<br> 4. Linking a prop of the component instance to a field<br> 5. Publishing the template<br> 6. Checking the published node and that the prop uses the field. Could be good to also check a second node that uses the same content template.<br> 7. Edit the template and add additional component instances to test multiple combinations of complexity on the Field Widget and <code>(Static|Dynamic)PropSource</code> axes: see <a href="https://git.drupalcode.org/project/canvas/-/merge_requests/56#note_587904">outline in this MR comment</a></p> <p>Another test that would be good to have is testing the flow when a user does not have any content yet. This could potentially be in another issue but noting here so it's not forgotten.</p> <h3 id="proposed-resolution">Proposed resolution</h3> <p>Take the approach of having a test be testing one use case versus repeating the same assertions of test setup. Consider creating a test recipe that will do steps 1-3 for the setup? Then have atomically-focused test testing each use case outlined in #7.</p> <h3 id="ui-changes">User interface changes</h3> > Related issue: [Issue #3541000](https://www.drupal.org/node/3541000)