I have run jest in the yarnpkg source tree with:
jest --ci __tests__/
having this jest.config.js to disable failing tests:
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 ..
Note:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2020-November/047062.html
Paolo
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
