Convert most browser functional tests to unit tests

Open
#146 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
testing-qa

Research direction

The issue does not name files or test entry points. Inspect the browser functional tests and separate the CSP tests from those that can be converted to unit tests under Intern 4; done means the eligible tests run as unit tests while CSP tests remain functional tests.

Written by the indexing model from the issue text.

Description

enhancement

Enhancement

In Intern 3, we wrote the browser tests using functional tests to get around Intern using an AMD loader when running unit tests. Since Intern 4 no longer requires an AMD loader, some of the functional tests could be rewritten as unit tests. I believe the only ones that would need to remain functional tests would be the CSP tests.

Dominant language
TypeScript
Stars
16
Forks
26
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dojo/loader

All issues in dojo/loader

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.