-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ts node support #245
Ts node support #245
Conversation
d060338 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Unfortunately I was still not able to get the existing tests running with the current master version of cds. Neither with jest 26 or 27. |
Yes, that's what I observe as well. Needs more investigation... |
@Kkoile can you allow edits from maintainers for this PR? |
I have not tested it in this repository, but in general, it seems to work with Jest using jasmine2 as test runner. With Jest 27, the default test runner was changed to jest-circus (see here). The problem is probably related to this. There were some changes that can lead to errors, see for example here. |
Had a closer look and some findings. Turns out there is an error on server startup that sap/cds swallows:
→ This actually looks like This changes if one configures the preset in package.json: "jest": {
"testEnvironment": "node",
"preset": "ts-jest"
} results in
Now something is wrong w/ the |
I have pulled this over to PR #248 in the original repo. |
No description provided.