Skip to content

Update the tooltip of the usage counter#22355

Merged
vraja-pro merged 2 commits intofeature/ai-generator-in-freefrom
630-update-the-tooltip-of-the-usage-counter
Jun 16, 2025
Merged

Update the tooltip of the usage counter#22355
vraja-pro merged 2 commits intofeature/ai-generator-in-freefrom
630-update-the-tooltip-of-the-usage-counter

Conversation

@igorschoester
Copy link
Copy Markdown
Contributor

Context

Summary

This PR can be summarized in the following changelog entry:

  • Without Premium, in the AI generator modal's tooltip: Don't mention unlimited sparks.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • Devs: use the fake API
  • Deactivate Premium
  • Edit a post and use AI
  • Verify the tooltip does not mention unlimited sparks
  • Activate Premium
  • Edit a post and use AI
  • Verify the tooltip mentions unlimited sparks

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes https://github.com/Yoast/reserved-tasks/issues/630

@igorschoester igorschoester added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Jun 16, 2025
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build b672547d049db5187e94e3d240cbc7bf7af90a2c

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 52.034%

Totals Coverage Status
Change from base Build f7aca60847beadb50d0cd992cd9d0c96d7b409b0: 0.0%
Covered Lines: 29976
Relevant Lines: 58673

💛 - Coveralls

@vraja-pro
Copy link
Copy Markdown
Contributor

CR & AC ✅

@vraja-pro vraja-pro merged commit caa8499 into feature/ai-generator-in-free Jun 16, 2025
19 of 21 checks passed
@vraja-pro vraja-pro deleted the 630-update-the-tooltip-of-the-usage-counter branch June 16, 2025 13:11
@pls78 pls78 mentioned this pull request Jul 15, 2025
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants