Endform logo

Changelog

Latest updates and improvements to Endform.

This week brings major improvements to how Endform handles Playwright configurations, with support for nested configs and comprehensive trace options. CLI 0.42.x includes a significant internal rewrite that makes Endform work more naturally with Playwright’s file system conventions.

Major features & improvements

  • Complete trace mode support: All of Playwright’s trace options are now supported, including advanced modes like on-first-retry and retain-on-first-failure. Previously Endform only supported basic options like on, off, and retain-on-failure.

CLI version updates

Version 0.42.x

  • Full trace mode support: All Playwright trace options are now supported, including on-first-retry, on-all-retries, retain-on-first-failure, and other advanced trace modes.

  • Nested Playwright config support: Playwright configurations can now live in nested directories instead of requiring them at the same level as package.json. The CLI uses a new path system that understands Playwright’s multiple reference points (config directory, test root, package.json location, and repository root).

  • Improved Playwright config handling: The CLI now transfers your Playwright config as-is to remote runners instead of pre-serializing it, allowing for better dynamic configuration.

This week brings Playwright 1.56 compatibility to endform.

Major features & improvements

  • Playwright 1.56 support: Endform now fully supports Playwright 1.56, ensuring you can use the latest features and improvements from Playwright’s newest release.

CLI version updates

Version 0.41.x

  • Improved symbolic link handling: Projects with multiple major versions of the same nested dependency now work correctly.
  • Better dry-run accuracy: The --dry-run flag now creates dependency zips that more closely match what would actually be uploaded to Endform, giving you more accurate previews before running tests
  • Smarter optional dependency handling: The CLI now only downloads optional dependencies that are OS or architecture-specific (like native binaries), avoiding unnecessary re-downloads of JavaScript-based optional dependencies that already exist in node_modules
  • Enhanced package.json resolution: Switched to using OXC’s native package.json positioning instead of custom resolution logic, improving reliability for complex project structures

This week brings major improvements to test asset handling with full snapshot and screenshot support in CLI 0.41.x, plus several dashboard enhancements including a new changelog page and a pending invitations UI.

Major features & improvements

  • Snapshot & screenshot support: The CLI now fully supports Playwright snapshots, screenshots, and similar test assets. These files are automatically tracked as dependencies per test, and any changes made during test runs are properly synchronized back from the remote runners. This makes visual regression testing and snapshot-based testing work seamlessly with Endform’s remote execution.

  • Team invitations: Pending team invitations are now visible in the dashboard header and on the new organization page, making it easier to manage your team access.

CLI version updates

Version 0.41.x

  • Snapshot & screenshot support: The CLI now fully supports Playwright snapshots, screenshots, and similar test assets. 👆

  • Improved support for complex testing setups: Enhanced handling of optional dependencies, Playwright configurations, and Chromium browser arguments to support more diverse testing layouts and reduce setup complexity.

CLI version updates

Version 0.40.x

  • Max failures configuration: Added support for Playwright’s maxFailures configuration option, giving you more control over when test runs should stop based on failure thresholds.

  • JSON import support: Improved support for importing JSON files in your tests, with better parsing and dependency tracking to ensure all necessary files are uploaded for test execution.

  • Teardown projects: Better support for Playwright teardown projects, ensuring cleanup operations run reliably at the end of your test suites.