Premium Analytics: run JavaScript tests in CI

[chihsuan]

Related to WOOA7S-1717

Proposed changes

Premium Analytics already has a JavaScript test suite, but the package does not expose a Composer test-js script. The standard Jetpack JS test job therefore skips the package.

• Add test-js so the existing suite runs in CI.
• Refresh only the Composer lockfiles that embed Premium Analytics package metadata.
• Keep this CI configuration separate from the widget availability changes in Premium Analytics: show File downloads only on WPCOM Simple sites #50732.

Related product discussion/links

• WOOA7S-1717
• Premium Analytics: show File downloads only on WPCOM Simple sites #50732

Does this pull request change what data or activity we track or use?

No.

Testing instructions

1. Run pnpm install --frozen-lockfile.
2. Run pnpm jetpack test js packages/premium-analytics.
3. Confirm all Premium Analytics JavaScript tests pass.
4. Run the Composer monorepo update tool for the Premium Analytics, mu-wpcom-plugin, and wpcomsh plugin lockfiles.
5. Confirm each reports Nothing to modify in lock file.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (WordPress.com Site Helper), and enable the chore/premium-analytics-enable-js-tests branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack-mu-wpcom-plugin chore/premium-analytics-enable-js-tests

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Mu Wpcom plugin:

• Next scheduled release: WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2)

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Wpcomsh plugin:

• Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Premium Analytics plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[anomiex]

Please add a test-js-coverage command too.

Suggested change

	"test-js": "pnpm run test",
	"test-js": "pnpm run test",
	"test-js-coverage": "pnpm run test --coverage",

Then it looks like you'll also need to update projects/packages/premium-analytics/tests/jest.config.cjs to actually generate coverage, since the needed paths aren't in the default collectCoverageFrom.

Or maybe we should just add the additional wp-build paths to collectCoverageFrom in tools/js-tools/jest/config.coverage.js, since other projects will need them too.

P.S. You should be able to test the coverage locally with jetpack test js-coverage -v packages/premium-analytics.

[anomiex]

Or maybe we should just add the additional wp-build paths to collectCoverageFrom in tools/js-tools/jest/config.coverage.js, since other projects will need them too.

I went ahead and did that in #50782.