feat: add new package @wdio/image-comparison-core (#982) #994
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π₯ Major Release: New @wdio/image-comparison-core Package
ποΈ Architectural Refactor
This release introduces a completely new core architecture with the dedicated
@wdio/image-comparison-core
package, replacing the genericwebdriver-image-comparison
module with a WDIO-specific solution.What was the problem?
webdriver-image-comparison
package was designed for generic webdriver usageWhat changed?
β New dedicated core package:
@wdio/image-comparison-core
- purpose-built for WebdriverIOβ Cleaner architecture: Modular design with clear separation of concerns
β Enhanced test coverage: Improved from ~58% to ~90% across all metrics
β Better maintainability: Organized codebase with comprehensive TypeScript interfaces
β WDIO-specific dependencies: Only depends on
@wdio/logger
,@wdio/types
, etc.π§ͺ Testing Improvements
π§ Service Integration
The
@wdio/visual-service
now imports from the new@wdio/image-comparison-core
package while maintaining the same public API and functionality for users.π Performance & Quality
π Backward Compatibility
β No breaking changes for end users
β Same public API maintained
β Existing configurations continue to work
β All existing functionality preserved
π― Future Benefits
This refactor sets the foundation for:
π¦ Dependency Updates
Note: This is an architectural improvement that modernizes the codebase while maintaining full backward compatibility. All existing functionality remains unchanged for users.