Skip to content

Migrate JavaScript test framework to more popular alternative #432

Open
@gnikonorov

Description

@gnikonorov

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    code qualityThis PR has to do with improving code readability/quality ( refactoring, etc. )next-genCandidate for the next-gen projecttestThis PR relates to tests, QA, CI.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions