#37117 closed defect (bug) (fixed)
Upgrade QUnit to 2.9.x
| Reported by: | jorbin | Owned by: | SergeyBiryukov |
|---|---|---|---|
| Priority: | normal | Milestone: | 5.5 |
| Component: | Build/Test Tools | Version: | |
| Severity: | normal | Keywords: | 2nd-opinion has-patch |
| Cc: | Focuses: |
Description
QUnit 2.0.0 has been released. There is a upgrade guide to assist in the migration.
Attachments (1)
Change History (8)
#2
@
7 years ago
2.9.2
trentmwillis released this 19 days ago · 4 commits to master since this release
#3
@
7 years ago
- Keywords 2nd-opinion added
Is there anything in newer versions of QUnit that we particularly need? The QUnit tests really haven't evolved or expanded in recent years.
Alternatively, Gutenberg has a well developed test library based on Jest, and exports all of the config as a package we could use. In the interest of standardising, perhaps the better option would be migrate our existing QUnit tests to work in Jest, instead.
#4
@
6 years ago
- Keywords has-patch added
- Milestone Awaiting Review → 5.5
- Owner set to
- Status new → accepted
- Summary Upgrade QUnit to 2.3.2 → Upgrade QUnit to 2.9.x
While migrating our existing QUnit tests to work in Jest seems like good idea, updating to the latest QUnit seemed like a good first step for me to get more familiar with them. Started this as an experiment, which turned out to be successful.
In 37117.diff:
- Update QUnit and Sinon to the latest versions.
- Remove the abandoned
sinon-qunitscript (added in [27846]). - Update the tests per the QUnit 2.x Upgrade Guide.
- The tests pass: https://travis-ci.com/github/SergeyBiryukov/wordpress-develop/jobs/302244802
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
The current version of QUnit is now
2.3.2.