Closed TarunAdobe closed 1 month ago
Category | Latest (report) | Main (report) | Branch (report) |
---|---|---|---|
Performance | 0.99 | 0.99 | 0.99 |
Accessibility | 1 | 1 | 1 |
Best Practices | 1 | 1 | 1 |
SEO | 1 | 0.92 | 0.92 |
PWA | 1 | 1 | 1 |
main
("Main"). Higher scores are better, but *note that the SEO scores on Netlify URLs are artifically constrained to 0.92.*
Category | Latest | Main | Branch |
---|---|---|---|
Total | 221.156 kB | 210.144 kB π | 210.552 kB |
Scripts | 53.319 kB | 47.969 kB π | 48.349 kB |
Stylesheet | 34.999 kB | 30.381 kB | 30.356 kB π |
Document | 5.892 kB | 5.188 kB π | 5.195 kB |
Font | 126.946 kB | 126.606 kB π | 126.652 kB |
Category | Latest | Main | Branch |
---|---|---|---|
Total | 45 | 45 | 45 |
Scripts | 37 | 37 | 37 |
Stylesheet | 5 | 5 | 5 |
Document | 1 | 1 | 1 |
Font | 2 | 2 | 2 |
Description
This PR adds more tests to SWC components in order to improve the overall code coverage across the library. The simple criteria that I'm following here is to have a >95% code coverage for every component.
Motivation and context
Recently we have added a lot of
Dev Mode
warnings for in our library but didn't add respective tests for that which caused the ci to fail in main.How has this been tested?
Screenshots (if appropriate)
Types of changes
Checklist
Best practices
This repository uses conventional commit syntax for each commit message; note that the GitHub UI does not use this by default so be cautious when accepting suggested changes. Avoid the "Update branch" button on the pull request and opt instead for rebasing your branch against
main
.