Add tests for the addition of cached data in the dashboard frontend package

[leonidasmi]

Context

• Brings the test coverage of the dashboard-frontend package back to 95% lines.

Summary

This PR can be summarized in the following changelog entry:

• Follows up the addition of cached data in the dashboard package, by adding tests.

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:

• N/A

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.

Impact check

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

• No impact

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/515

[coveralls]

Pull Request Test Coverage Report for Build 91b9a4994deeba5f197c52928f328466f14ced00

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.1%) to 52.898%

---

Totals
Change from base Build c122b65f10dc870041aa32063f370fb2a203577e:	0.1%
Covered Lines:	29606
Relevant Lines:	57106

---

💛 - Coveralls

[igorschoester]

CR 🏗️

P.S. your PR is still in draft.

[igorschoester]

Some branches are not covered.
I can recommend running coverage and checking out the report for details.

File	% Stmts	% Branch	% Funcs	% Lines	Uncovered Line #s
cache.js	90	66.67	100	90	59,69,200-208

Code coverage report for src_services_cache.js (5_6_2025 11：07：40 AM).html.zip

[leonidasmi]

Brought branch coverage to 80% with this commit. I've tried to mock the storage API functions, to increase it even more to no avail.

[igorschoester]

Here is an example of getting to test the exception for an error when the storage is exceeded:

	it( "should return the storage also when quota exceeded", () => {
		global.FakeStorage = {
			setItem: jest.fn().mockImplementation( () => {
				throw new DOMException( "code 22", "QuotaExceededError" );
			} ),
			removeItem: jest.fn(),
			length: 1,
		};
		setStorageOrder( [ "FakeStorage" ] );

		try {
			expect( getStorage() ).toEqual( global.FakeStorage );
			expect( global.FakeStorage.setItem ).toHaveBeenCalled();
		} finally {
			// Clean up the fake storage.
			delete global.FakeStorage;
		}
	} );

Not sure how far you actually want/need to go. But if it is because you didn't know how, this should help.