jquery / jquery/jquery-migrate
Migrate meant to aid upgrading to jQuery n should have tests run on jQuery n-1
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.1k
- Forks
- 476
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
We should verify that Migrate meant to aid migration from jQuery n-1 to n passes as much as possible from the jQuery n-1 test suite. One idea is to commit the test/ directory from the Core repo's proper branch and comment out or QUnit.skip tests that are broken and we don't know how to quickly fix them (maybe creating issues for those that are possible but hard to fix). That way we'd at least know we don't regress; currently the test coverage of the whole jQuery + Migrate combination is pretty low.
cc @dmethvin & @gibson042 which discussed this idea with me on IRC.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the jQuery Core test/ directory from the appropriate jQuery n-1 branch and compare it with the current Migrate test setup. Run the combined jQuery and Migrate tests, identify tests that fail during migration coverage, and use QUnit.skip for failures that cannot be addressed quickly. Done means the suite runs against jQuery n-1 and regressions are visible, with harder failures tracked separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100