Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add Coveralls github workflow #759

Merged
merged 2 commits into from
May 12, 2021
Merged

add Coveralls github workflow #759

merged 2 commits into from
May 12, 2021

Conversation

oshi97
Copy link
Contributor

@oshi97 oshi97 commented May 7, 2021

Adds a code coverage workflow using Coveralls
Only static .js files have their coverage collected.
Trying to collect code coverage from hbs files masquerading
as js files causes the coverage reporter to crash, since it
can't parse the hbs portions of the file correctly.

Also adds a code coverage badge to the readme.

J=SLAP-873
TEST=auto

Adds a code coverage workflow using Coveralls
Only static .js files have their coverage collected.
Trying to collect code coverage from hbs files masquerading
as js files causes the coverage reporter to crash, since it
can't parse the hbs portions of the file correctly.

Also adds a code coverage badge to the readme.

J=SLAP-873
TEST=auto
with:
node-version: ${{ matrix.node-version }}
- run: npm ci
- run: npx jest --coverage
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we only generate coverage for tests/static/**/*.js, could we just run the jest tests in that directory?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes that makes sense!

@oshi97 oshi97 requested review from tmeyer2115 and cea2aj May 10, 2021 20:36
@oshi97 oshi97 merged commit 94c60fe into develop May 12, 2021
@oshi97 oshi97 deleted the dev/coveralls branch May 12, 2021 14:30
@cea2aj cea2aj mentioned this pull request Jun 23, 2021
cea2aj added a commit that referenced this pull request Jun 23, 2021
## Version 1.22.0
### Changes
- Code coverage reports are now generated automatically for the Theme. (#759)
- A number of dependencies were updated in accordance with Dependabot's suggestions. (#780)
- The build time in `Development` mode was reduced significantly. (#782, #829) Build times in 
`Production` mode were also decreased. (#783, #825)
- Two new cards supporting videos were added: `product-prominentvideo` and `multilang-product-prominentvideo`. These cards
work with either YouTube or Vimeo content. (#794)
- The process for formatting hours was made more efficient, resulting in faster renders for cards with hours. (#784)
- Any SDK branch can now be specified in the `global_config.sdkVersion` attribute. (#791)
- Unused CSS was removed from the Theme. (#793, #798)
- To reduce flashing related to the SDK Component lifecycle, placeholder skeletons were added for the `SearchBar` and
`Navigation` components. (#797)
- Additional acceptance tests were added for the `VerticalFullPageMap` and Percy snapshots are now generated for all
cards. (#830, #820)
- Multi-language tests were added for the Theme. (#826)
- The `documentsearch-standard` card now supports rich text featured snippets. (#838)
- A new concept, `RuntimeConfig` was added. This allows configuration, computed at run-time, to be injected into the
Theme and SDK. This new concept enables JWT integrations as well. (#843)
### Bug Fixes
- A number of changes were made to make the Theme's visual regression tests more reliable. (#764, #765, #766, #778)
- Corrected how the CTA URLs for the `menuitem-standard` and `multilang-menuitem-standard` cards are computed. (#787)
- The Google Streetview person icon is now visible when using the `VerticalFullPageMap` layout. (#801)
- The size of the cluster and result pins are now configurable. (#807)
- A double encoding error for `verticalUrl` was fixed. (#836)
- The `Opens At` open status message is now properly translated in all languages. (#834)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants