[Pkg-javascript-devel] Bug#940704: Bug#940704: some tests do pass

Pirate Praveen praveen at onenetbeyond.org
Thu Dec 24 19:07:29 GMT 2020



On Thu, Dec 24, 2020 at 19:50, Paolo Greppi <paolo.greppi at libpf.com> 
wrote:
> I have run jest in the yarnpkg source tree with:
> jest --ci __tests__/
> 

You can add this to debian/tests/pkg-js/test

> having this jest.config.js to disable failing tests:
> 
and include this as a patch.

> module.exports = {
>   testURL: "http://localhost/",
>   testPathIgnorePatterns: [
>     "<rootDir>/node_modules/",
>     "<rootDir>/__tests__/index.js",
>     "<rootDir>/__tests__/integration.js",
>     "<rootDir>/__tests__/lifecycle-scripts.js",
>     "<rootDir>/__tests__/pipe.js",
>     "<rootDir>/__tests__/commands/pack.js",
>     "<rootDir>/__tests__/commands/run.js",
>     "<rootDir>/__tests__/fixtures",
>     "<rootDir>/__tests__/reporters/_mock.js",
>     "<rootDir>/__tests__/commands/_helpers.js",
>     "<rootDir>/__tests__/_temp.js",
>     "<rootDir>/__tests__/__mocks__",
>     "<rootDir>/__tests__/commands/install/lockfiles.js"
>   ]
> }
> 
> result:
> Test Suites: 1 skipped, 81 passed, 81 of 82 total
> Tests:       15 skipped, 1116 passed, 1131 total
> Snapshots:   111 passed, 111 total
> Time:        74.936s
> Ran all test suites matching /__tests__\//i.
> 
> I think we can include it in the autopkgtest, later we can try to 
> understand why some tests are failing ..
> 
yes, running some tests soon while we figure out what is wrong with the 
rest is a good idea.

> Note: 
> https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2020-November/047062.html
> 
> Paolo



More information about the Pkg-javascript-devel mailing list