Forms: Tests: Shouldn't submit if empty

[lezama]

Extracted from #41356

Proposed changes:

• Add test to verify that contact forms don't submit when all fields are empty
• This test was originally part of PR Forms: Require at least one field #41356 but has been extracted since we went with PR Forms: Prevent empty form submission client side #41464 for the main implementation
• The test helps ensure proper form validation behavior

Jetpack product discussion

N/A - This is a test-only change extracted from a previously discussed PR

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

No - This PR only adds test coverage

Testing instructions:

• run the js tests jetpack test for the form package
• Verify that the new test shouldn't submit when all fields are empty passes
• The test should confirm that a form with empty fields does not submit

[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 WordPress.com Simple 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, and enable the add/forms-test branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack add/forms-test
  

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

[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 Team Review, ...).
  
• 🔴 Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[github-actions]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/contact-form/js/accessible-form.js	240/375 (64.00%)	16.53%	-62 💚

Full summary · PHP report · JS report

[simison]

Is this ready for review?

[lezama]

Is this ready for review?

yes 😄

[simison]

Just a nit on test name but otherwise looking fine.