Testing Cookie Consent Across SPA Route Changes: A Practical QA Checklist

Why Cookie Consent Testing Matters in Single-Page Applications

Single-page applications (SPAs) provide smooth navigation without reloading the entire website. However, this behavior can create challenges when testing cookie consent preferences.

A visitor may reject cookies on the homepage, but what happens when they navigate to another page without a full reload?

This is an important scenario for QA teams and developers to test.

1. Check Consent After the First Visit

Open the website in a fresh browser session.

• Check whether the consent banner appears.
• Review the available options, such as Accept, Reject, and Manage Preferences.
• Confirm that each option works as expected.

1. Test Navigation Between Routes

After selecting Reject, navigate to different sections of the application.

For example:

• Homepage to Pricing
• Pricing to About Us
• About Us to Contact

Check whether the saved consent choice remains consistent across these routes.

1. Verify Consent Persistence

Refresh the page and revisit the website.

Check:

• Whether the consent banner appears again.
• Whether the previous preference is restored.
• Whether the stored consent state matches the visitor's selection.

The expected behavior should be based on the website's consent configuration.

1. Test Preference Changes

Visitors may change their minds.

Test whether a user can update their choice from Reject to Accept or modify individual preferences through the settings panel.

Verify that the updated choice is reflected after navigation and refresh.

1. Check Network Requests Carefully

Do not assume that every network request means consent is broken.

The expected behavior depends on the consent-management configuration and the tracking technology being used.

For example, Google Consent Mode has different behaviors in Basic and Advanced implementations. QA teams should verify the actual consent state and tag behavior instead of judging only by the presence of network requests.

1. Common Issues to Watch For

During testing, look for problems such as:

• Consent preferences not restored after route changes.
• Banner appearing repeatedly.
• Old preferences being displayed after an update.
• Different consent behavior between routes.
• Tracking tags behaving differently from the configured consent state.

1. Maintain a Clear Test Record

For every test, record:

• Browser and version
• Website build or environment
• Initial consent selection
• Navigation steps
• Expected result
• Actual result
• Screenshots or other evidence

This makes bugs easier to reproduce and investigate.

Final Thoughts

Cookie consent testing should not stop after checking whether the banner appears.

In single-page applications, QA teams should also verify route changes, saved preferences, refresh behavior, and updates to consent choices.

A consistent testing process helps identify issues that may otherwise go unnoticed during basic functional testing.