pytest-dev / pytest-dev/pytest-html
Migrate JavaScript test framework to more popular alternative
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 779
- Forks
- 260
- PR merge metrics
- No merged PRs in 30d
Description
We currently use QUnit for unit testing our JavaScript.
I propose that we move to a more modern testing framework ( the top five listed here seem to pop up a bit ).
I would like to add that any library we migrate to should have good support for testing URL parameters. QUnit forces the definition of one test script per URL which I think isn't ideal, since it's pretty cumbersome: https://stackoverflow.com/questions/27388596/pass-url-parameter-to-qunit-test-using-grunt
As a follow up, tests should be written for all URL parameters, since we currently have 0 tests for them.
@BeyondEvil maybe this is something we could tackle as part of the next gen migration?
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the existing QUnit setup and how URL parameters are currently tested; no file or test path is named in the issue. Compare candidate JavaScript testing frameworks for URL-parameter support, then define migration scope and add coverage for all URL parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100