Skip to content

Track FTC progress#22677

Merged
enricobattocchi merged 1 commit intorelease/26.3from
enrico/track-ftc-progress
Oct 28, 2025
Merged

Track FTC progress#22677
enricobattocchi merged 1 commit intorelease/26.3from
enrico/track-ftc-progress

Conversation

@enricobattocchi
Copy link
Copy Markdown
Member

@enricobattocchi enricobattocchi commented Oct 28, 2025

Context

Summary

This PR can be summarized in the following changelog entry:

  • Adds the state of the FTC completion progress to the tracked options.

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:

  • NA

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:

  • NA

Impact check

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

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 #

@enricobattocchi enricobattocchi added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Oct 28, 2025
@enricobattocchi enricobattocchi force-pushed the enrico/track-ftc-progress branch from 50bd212 to 1196835 Compare October 28, 2025 14:21
@enricobattocchi enricobattocchi added this to the 26.3 milestone Oct 28, 2025
@enricobattocchi enricobattocchi merged commit 54e00bb into release/26.3 Oct 28, 2025
26 checks passed
@enricobattocchi enricobattocchi deleted the enrico/track-ftc-progress branch October 28, 2025 14:31
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 0d12235bb79c03078948964cb84748e21d263c19

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall first build on enrico/track-ftc-progress at 49.475%

Totals Coverage Status
Change from base Build c903b3e0efd8951c873ed7caaddd13fdcf7d17cc: 49.5%
Covered Lines: 17448
Relevant Lines: 35266

💛 - Coveralls

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.

2 participants