4.8.0 Release

[jennifer-shehane]

• 4.8.0 Changelog
• Section for new spec file header Section for new spec file header in TR #2852
• Update screenshots for error design changes Update errors for design changes #2853
• Test config options + isBrowser() changes Test/Suit configuration options + Cypress.isBrowser updates #2697
• Update wording around 'test options' / 'test config'
• experimentalShadowDom experimental flag Add shadow dom experimental flag #2858

---

Preview of main content for 'test config' feature

[brian-mann]

I believe that we are not sufficiently highlighting the browser test configuration override.

It's mentioned in the isBrowser API (although way at the bottom and underneath all of the other use cases, even though it is the primary use case of that method.

It's also mentioned in the cross browser doc, but I feel like it should be mentioned in the configuration area, or somewhere with more real estate.

[CypressCecelia]

@jennifer-shehane There's a typo in the Test Configuration documentation in the screenshot (couldn't find where the actual file was changed, I think that's a separate PR). In the "Note" with the red caution sign, the second sentence says

"The following...can be changed via per test configuration."

It should be either via or per, not both.

[brian-mann]

@jennifer-shehane There's a typo in the Test Configuration documentation in the screenshot (couldn't find where the actual file was changed, I think that's a separate PR). In the "Note" with the red caution sign, the second sentence says

"The following...can be changed via per test configuration."

It should be either via or per, not both.

Maybe:

• by individual test configuration
• with individual test configuration
• by specific test configuration
• with specific test configuration

[flotwig]

couldn't find where the actual file was changed, I think that's a separate PR

same, can't find it, so let's go ahead with this PR as-is for now since it's not in this PR