Skip to content

Testing Instructions for Critical Flow

Jump to bottom
Ankit K Gupta edited this page Jan 4, 2024 · 9 revisions

Please follow the below instructions to execute/run cases mentioned in the critical flow.

Admin can activate the plugin without error

The plugin should be installed and activated without any error or trouble.

Steps:

  1. Download the Plugin zip file.
  2. Install the plugin zip in the Plugin Uploader screen of the site.

Expected Result-

The plugin should be installed without any error.

Plugin should show an error message when activating the un-supported PHP version.

Steps:

  1. Downgrade PHP version if using =< PHP 7.4
  2. Activate the plugin

Expected Result-

  1. Plugin should show a warning notice on activation.
  2. Plugin setup/setting buttons should not appear.

Screenshot 2023-12-18 at 8 11 55 PM

Plugin Activation Banner Display

Steps:

  1. Navigate to the WordPress admin dashboard.
  2. Go to the "Plugins" section.
  3. Locate and activate the ClassifAI plugin.

Expected Result-

Upon successful activation, a banner should be displayed in the header area.

  1. The banner text should have: "Congratulations, the ClassifAI plugin is now activated".
  2. The banner should include a button labelled 'Start Setup'.

NLU - Classify Content Setting Check - Admin Screen Settings

The objective of this test case is to ensure the functionality and configuration of the NLU (Natural Language Understanding) - Classify Content settings on the admin screen.

Steps:

  1. Navigate to WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Check the setting 'Classify Content'.
  3. Scroll to the bottom of the setting page and enable the setting 'Post Types to Classify'.
  4. Select 'Post' and 'Pages'.
  5. Enable checkbox for 'Category' and select 'Watson Category' from the dropdown.
  6. Save the setting by clicking the 'Save Changes' button.

Expected Result:

  1. The 'Classify Content' setting should be visible.
  2. The 'Post Types to Classify' setting should be present at the bottom of the page.
  3. 'Post' and 'Pages' should be selectable options for content classification.
  4. After saving changes, there should be a success message indicating that the changes were saved successfully.
  5. The settings should persist after saving, and the selected post types should remain enabled.

NLU - Classify Content Setting Check - Setting Output on Post/Page Screen

The objective of this test case is to ensure the functionality and configuration of the NLU (Natural Language Understanding) - Classify Content settings on the page and post screen.

Steps:

  1. Navigate to WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Check the setting 'Classify Content'.
  3. Scroll to the bottom of the setting page and enable the setting 'Post Types to Classify'.
  4. Select 'Post' and 'Pages'.
  5. Enable checkbox for 'Category' and select 'Watson Category' from the dropdown.
  6. Save the setting by clicking the 'Save Changes' button.

Expected Result:

  1. Navigate to WP Dashboard > Pages or Posts
  2. Open any Post/Page or create a new Post/Page
  3. Look at Post/Page editor right-hand sidebar section
  4. 'Watson Categories' section should appear.

NLU - Verify Setting 'Enable Role-Based Access'

Steps:

  1. Navigate to WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Check the setting 'Enable Role-Based Access'.
  3. The user role list should open, displaying all WP roles.
  4. Enable a user role (for example editor) to use the Classify setting.
  5. Save the setting.

Expected Result:

After saving the setting, only the allowed user role (for example: editor)should have access to the Classify setting on the page/post edit screen.

NLU - Verify Setting 'Enable Role-Based Access' for User Side

Steps:

  1. Follow the steps from the previous test case: "NLU - Verify Setting 'Enable Role-Based Access.'"
  2. Create a new user with the editor user role.
  3. Create or edit a page/post using the newly created user.
  4. Observe the ClassifAI section in the sidebar.

Expected Result:

A user with the editor role should be able to see the ClassifAI settings in the sidebar when creating or editing a page/post.

Negative Test Case: NLU - Verify Setting 'Enable Role-Based Access' from User Side

Steps:

  1. Follow the steps from the previous test case: "NLU - Verify Setting 'Enable Role-Based Access.'"
  2. 'Enable Role-Based Access' setting is unchecked for the editor role.
  3. Create a new user with the editor user role.
  4. Create or edit a page/post using the newly created user.
  5. Observe the ClassifAI section in the sidebar.

Expected Result:

A user with the editor role should not be able to see the ClassifAI settings in the sidebar when creating or editing a page/post since the editor role is not checked in the 'Enable Role-Based Access' setting.

NLU - Verify Setting "Enable User-Based Access" for Classifying Content on Page/Posts

Steps:

  1. Navigate to WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Check the setting "Enable User-Based Access."
  3. Option to select users will be displayed.
  4. Select a user to enable for Classifying Content.
  5. Save the setting.
  6. Log in with the selected user account.
  7. Create or edit a page/post.
  8. Observe the ClassifAI section in the sidebar.

Expected Result:

After saving the setting and logging in with the selected user account, the user should be able to see the ClassifAI settings in the sidebar when creating or editing a page/post.

NLU - Verify Setting "Enable User-Based Opt-Out" for opting out Classifying feature.

Steps:

  1. Navigate to WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Check the setting "Enable User-Based Opt-Out."
  3. Save the setting.
  4. Log in with any other user account.
  5. Go to the user profile page for the selected user.
  6. Look for the option to opt-out from Classifying Content.

Expected Result:

  1. After saving the setting and logging in with the selected user account, the user should be able to see an option to opt-out from Classifying Content on their user profile page.
  2. After enabling the setting 'Opt out of using the classify content feature.' user should not see the ClassifAI features on edit/new post/page.

NLU - Verify Setting Post Types to Classify

Test Steps:

  1. Navigate to the WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Access the 'Post Types to Classify' setting.
  3. Activate the Classify feature for a specific post type (e.g., WP Post).
  4. Save the setting to apply changes.
  5. Log in as a user with post/page management access.
  6. Open a post that has been enabled in the setting, such as a WP Post.

Expected Result:

The Classify setting should be visible in the sidebar, indicating that the classification feature is available for the selected post type.

NLU - Negative Test - Verify Setting 'Post Types to Classify'

Test Steps:

  1. Navigate to the WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Access the 'Post Types to Classify' setting.
  3. Ensure that the Classify feature is disabled for all post types.
  4. Save the setting to apply changes.
  5. Log in as a user with post/page management access.
  6. Open a post type that has been disabled for classification (e.g., WP Post).

Expected Result:

The Classify setting should not appear in the sidebar of WP Post Type., indicating that the classification feature is not available for the selected post type. This ensures that the negative scenario is correctly handled, and users are unable to access the classification feature for post types that have not been enabled in the setting.

NLU - Test Case for Classify Feature for Custom Post Type

Test Steps:

  1. Navigate to the WP Dashboard > Tools > ClassifAI > Language Processing > IBM Watson > Natural Language Understanding Screen.
  2. Access the 'Post Types to Classify' setting.
  3. Create a new Custom Post Type (e.g., Poems.) Refer to this guide if the site doesn't have any CPT
  4. Enable the Classify feature for a custom post type (e.g., Poems.)
  5. Save the setting to apply changes.
  6. Log in as a user with post/page management access.
  7. Create a new post of the custom post type Poems.

Screenshot 2024-01-03 at 8 57 34 PM

Expected Result:

  1. Newly created CPT should be visible in the list of options of Post Types to Classify.
  2. The Classify setting should be visible in the sidebar when editing the post of the custom post type e.g., Poems.

NLU - To verify that the NLU Taxonomies options work as expected on the setting page.

Test Steps:

  1. Navigate to the WP Dashboard.
  2. Go to 'Tools' > 'ClassifAI' > 'Language Processing' > 'IBM Watson' > 'Natural Language Understanding' Screen.
  3. Ensure that checkbox options for Category, Keyword, Entity, and Concept are available.
  4. Select the option for any taxonomy (e.g., Category).
  5. Set the Threshold value for the taxonomy.
  6. Select the Category Taxonomy option from the dropdown(e.g., Watson Category)
  7. Save the changes.
  8. Navigate to the 'Preview Language Processing' screen.

Expected Result:

  1. Verify that all enabled taxonomy(ies) (e.g., Category) appear under the 'Preview Language Processing' screen.
  2. The selected taxonomy appears in the preview, indicating a successful setup.

To verify that only enabled taxonomies appear under Post/Pages for ClassifAI.

Test Steps:

  1. Navigate to the WP Dashboard.
  2. Go to 'Tools' > 'ClassifAI' > 'Language Processing' > 'IBM Watson' > 'Natural Language Understanding' Screen.
  3. Enable some taxonomies (e.g., Category) for ClassifAI.
  4. Save the changes.
  5. Navigate to a 'Post' or 'Page' creation/editing screen.
  6. Check the available taxonomies for classification in the sidebar
Setting Page Editor
Screenshot 2024-01-04 at 5 01 04 PM Screenshot 2024-01-04 at 5 07 27 PM

Expected Result:

Only the enabled taxonomies (e.g., Category) appear for classification.

To verify that the 'Automatically Tag Content on Update' setting correctly fills taxonomy fields when enabled on the post/page editor.

Test Steps:

  1. Navigate to the WP Dashboard.
  2. Go to a 'Post' or 'Page' creation/editing screen.
  3. Locate the 'Automatically Tag Content on Update' setting.
  4. Enable the 'Automatically Tag Content on Update' setting.
  5. Update the content of the post/page.
  6. Check the respective taxonomy fields after the update.

Expected Result:

The taxonomy fields should be automatically filled with relevant tags based on the updated content when the 'Automatically Tag Content on Update' setting is enabled.

To verify that, when the 'Automatically Tag Content on Update' setting is disabled, the 'Suggest Terms & Tags' button is enabled on the post/page editor.

Test Steps:

  1. Navigate to the WP Dashboard.
  2. Go to a 'Post' or 'Page' creation/editing screen.
  3. Locate the 'Automatically Tag Content on Update' setting.
  4. Ensure the 'Automatically Tag Content on Update' setting is disabled.
  5. Check the status of the 'Suggest Terms & Tags' button.

Screenshot 2024-01-04 at 7 37 59 PM

Expected Result:

The 'Suggest Terms & Tags' button should be enabled, allowing users to manually suggest terms and tags when the 'Automatically Tag Content on Update' setting is disabled.

To verify that the 'Confirm Post Classification' pop-up appears when clicking the 'Suggest Terms & Tags' button on the post/page editor.

Test Steps:

  1. Navigate to the WP Dashboard.
  2. Go to a 'Post' or 'Page' creation/editing screen.
  3. Locate the 'Suggest Terms & Tags' button.
  4. Click on the 'Suggest Terms & Tags' button.
Screenshot

Screenshot 2024-01-04 at 7 43 30 PM

Expected Result:

A 'Confirm Post Classification' pop-up should appear, requesting confirmation before proceeding with term and tag suggestions. The pop-up should provide options to add or remove terms.

Clone this wiki locally