Skip to content

Should CI run more than test:browser? #1126

@chasenlehara

Description

@chasenlehara

Right now, Travis only runs the test:browser script:

- npm run test:browser

The test script has a lot more in it:

"test": "npm run jshint && npm run mocha && npm run test:browser && npm run test:slim-worker-single && npm run test:slim-worker-progressive && npm run test:exports-worker",

I added release scripts and only included test:browser in the preversion script because other tests weren’t passing for me locally.

"preversion": "npm run jshint && npm run test:browser",

Is this expected? Should CI run other tests too? What should be run locally?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions