-
Notifications
You must be signed in to change notification settings - Fork 20
Testing instructions for critical flows
Sumit Bagthariya edited this page Aug 12, 2024
·
7 revisions
Preconditions:
- WordPress installation with Classic Editor activated
- Convert to Blocks plugin installed and activated
- A post with content created in Classic Editor
Test Steps
- Download the Plugin zip from the Github
- Install the plugin zip in the Plugin Uploader screen of the store
Expected Result:
The plugin should be installed and activated without any error or trouble.
Test steps:
Description Check that Convert to Blocks transforms classic editor content into Gutenberg blocks
Test steps
- Log in to the WordPress admin dashboard.
- Create a new post in the classic editor
Expected result
- The Classic Editor content should be automatically transformed into corresponding Gutenberg blocks.
- The visual representation of the content should remain consistent with the original Classic Editor format.
Verifies that content converted from Classic Editor to Gutenberg blocks displays correctly on the frontend.
Test steps
- Log in to the WordPress admin dashboard.
- Create a new post in the classic editor
Expected result
- The converted Gutenberg blocks are rendered correctly on the frontend.
- The content displayed matches the content in the post editor.
- No layout or formatting issues are observed.
Test steps:
- Log in to the WordPress admin dashboard.
- Navigate to the Posts section.
- Select a post with content created in the Classic Editor.
- Click on the "Edit" button to open the post in the editor.
- Observe the post content.
- Make a change to the post content (e.g., add a new paragraph, modify existing text).
- Click the "Update" button to save the post.
Expected Result:
- The Classic Editor content is automatically converted to Gutenberg blocks when the post is opened for editing.
- The editor displays the content as editable Gutenberg blocks.
- The changes made to the post are reflected in the Gutenberg block structure.