You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> nextcloud@1.0.0 test
> jest core/
PASS core/src/tests/OC/requesttoken.spec.js
request token
✓ reads the token from the document (4 ms)
✓ remembers the updated token (1 ms)
@nextcloud/auth integration
✓ fires off an event for @nextcloud/auth (2 ms)
Test Suites: 1 passed, 1 total
Tests: 3 passed, 3 total
Snapshots: 0 total
Time: 1.335 s
Ran all test suites matching /core\//i.
With matching pattern
"test": "jest core/ --testRegex='[sS]pec.[tj]s'",
the result is much worse:
Test Suites: 15 failed, 1 passed, 16 total
Tests: 244 failed, 3 passed, 247 total
Snapshots: 0 total
Time: 7.081 s
I guess the tests were not adjusted since they were not executed anymore.
cc @nextcloud/server-frontend
The text was updated successfully, but these errors were encountered:
Looking into it with more expertise about NC front-end tests, it looks to me that everything is alright.
This PR introduced jest as a test runner to replace mocha, but there was only one test executed at the time. All the other tests are executed by karma.
Some big brain time here.
With some update the regex pattern of jest changed (
--testRegex
is available to configure it)To test
modify
server/package.json
Line 16 in 4322aab
to
Since then only one test in core is executed:
With matching pattern
the result is much worse:
I guess the tests were not adjusted since they were not executed anymore.
cc @nextcloud/server-frontend
The text was updated successfully, but these errors were encountered: