You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent refactor of auro-datepicker and adding the new date range feature, we need to write tests to cover the vendor files from wc-range-datepicker.
Possible Solution
Write the needed tests for those vendor files.
Context
When reviewing the code coverage for auro-datepicker, the data shows that almost none of those vendor files from wc-range-datepicker are being tested, bringing the overall code coverage of the component way down.
AC
These tests will be written once the new version of auro-datepicker is released.
The text was updated successfully, but these errors were encountered:
@jordanjones243 this is a weird situation. The code in the vendor dir is not specifically our code and I would not expect this team to write tests for vendor code.
For this initial release, I would think it's best to ignore the vendor dir. Moving forward we will be reviewing options for owning this code as either directly in this repo or creating a better dependency.
Exit criteria
Update test expectations that allow for ignoring all the code in the vendor dir.
Moved this last issue from the date range selection feature milestone to the new datepicker mobile experience milestone as there is no reason to NOT do this work.
General Support Request
Support request
With the recent refactor of auro-datepicker and adding the new date range feature, we need to write tests to cover the vendor files from
wc-range-datepicker
.Possible Solution
Write the needed tests for those vendor files.
Context
When reviewing the code coverage for auro-datepicker, the data shows that almost none of those vendor files from
wc-range-datepicker
are being tested, bringing the overall code coverage of the component way down.AC
These tests will be written once the new version of auro-datepicker is released.
The text was updated successfully, but these errors were encountered: