Closed avattipalli closed 1 month ago
Latest commit: b4d7eae43fc32641a3971761369bae33d17adca0
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
catalyst | 🔄 Building (Inspect) | Visit Preview | 💬 Add feedback | Jul 24, 2024 4:51pm |
catalyst-latest | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jul 24, 2024 4:51pm |
Lighthouse ran against https://catalyst-latest-qdtigvmz9-bigcommerce-platform.vercel.app
We ran Lighthouse against the changes on a desktop and produced this report. Here's the summary:
Category | Score |
---|---|
🟢 Performance | 91 |
🟢 Accessibility | 100 |
🟢 Best practices | 96 |
🟠 SEO | 82 |
We ran Lighthouse against the changes on a mobile and produced this report. Here's the summary:
Category | Score |
---|---|
🟠 Performance | 86 |
🟢 Accessibility | 100 |
🟢 Best practices | 96 |
🟠 SEO | 85 |
What/Why?
Add the option to generate code coverage in dev environment. We can generate the code coverage on the CI too but it currently requires to update the build process and make some updates based on the file map. I'll be following up with another change to handle this as part of CI.
With this change, we would also be using monocart-reporter as the test report. It is a better reporter than what we currently have setup.
Testing
Tested locally.
Code Coverage Report
Test run report