Jest Testing Errors

[snarkipus]

I don't think this is a Langium issue necessarily. I previously narrowed it down to a unresolved issue with jest-chain (#34) ... or at least I thought I had.

I'm not entirely sure when this broke (or how), but I'm constantly getting TypeError: result.message is not a function for failing tests in Jest.

I swear I resolved this once by simply rolling back the version of jest (like this), but that doesn't seem to work anymore and I narrowly avoided npm hell by trying. Is this something you all have observed?

[montymxb]

@snarkipus I've seen this pop up before on a separate project when working with jest-expect-message, but it's an elusive error. However, I haven't personally seen this show up in Langium myself. Is it possible something got stuck version-wise in node_modules?

[snarkipus]

Thanks @montymxb - I updated jest to 28.1.3 and did a clean install to no avail. I'm working from the latest commit in the github repo. Here's my dev deps from the package.json and the npm list output just in case something jumps out at you. Thanks for looking into it, I really appreciate it.

  "devDependencies": {
    "@types/jest": "^28.1.1",
    "@types/jest-expect-message": "^1.0.3",
    "@typescript-eslint/eslint-plugin": "^5.28.0",
    "@typescript-eslint/parser": "^5.28.0",
    "eslint": "^8.17.0",
    "eslint-plugin-header": "^3.1.1",
    "jest": "^28.1.1",
    "jest-expect-message": "^1.0.2",
    "shx": "^0.3.4",
    "ts-jest": "^28.0.5",
    "typescript": "^4.7.4"
  },

langium-workspaces@ /home/snarkipus/Projects/langium/langium-core/langium
├── @types/[email protected]
├── @types/[email protected]
├── @typescript-eslint/[email protected]
├── @typescript-eslint/[email protected]
├── [email protected]
├── [email protected]
├─┬ [email protected] -> ./packages/generator-langium
│ ├── @types/[email protected]
│ ├── @types/[email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├── [email protected]
├── [email protected]
├─┬ [email protected] -> ./examples/arithmetics
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected] deduped -> ./packages/langium-cli
│ ├── [email protected] deduped -> ./packages/langium
│ ├── [email protected]
│ └── [email protected]
├─┬ [email protected] -> ./packages/langium-cli
│ ├── @types/[email protected]
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected] deduped -> ./packages/langium
│ └── [email protected] deduped
├─┬ [email protected] -> ./examples/domainmodel
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ ├── [email protected] deduped -> ./packages/langium-cli
│ ├── [email protected] deduped -> ./packages/langium
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ └── [email protected] deduped
├─┬ [email protected] -> ./packages/langium-sprotty
│ ├── [email protected] deduped -> ./packages/langium
│ └── [email protected]
├─┬ [email protected] -> ./examples/statemachine
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ ├── [email protected] deduped -> ./packages/langium-cli
│ ├── [email protected] deduped -> ./packages/langium
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ └── [email protected] deduped
├─┬ [email protected] -> ./packages/langium-vscode
│ ├── @types/[email protected]
│ ├── [email protected]
│ ├── [email protected] deduped -> ./packages/langium
│ ├── [email protected] deduped
│ └── [email protected] deduped
├─┬ [email protected] -> ./packages/langium
│ ├── [email protected]
│ ├── [email protected] deduped -> ./packages/langium-cli
│ ├── [email protected]
│ ├── [email protected] deduped
│ └── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

[montymxb]

@snarkipus Hmm, interesting. Packages were a little different on my end for a clean install, but even matching them explicitly to yours does not replicate the issue 🤔 .

The next thing that comes to mind is your version of node & npm that's installed. Langium expects npm in the range 7.X.X, but in practice I've used npm 8.11.0 without issue -- coupled with node v16.15.1. It's possible if you're running an older version of node that there might be something odd going on. If you are on an older version, perhaps bumping up a bit might rectify the problem.

[snarkipus]

Perhaps it's something unique to my environment somehow. I"m not entirely sure.

Doing a clean install (npm ci) after setting npm to 8.11.0 (npm install -g [email protected]) and setting node to 16.15.1 (nvm install 16.15.1) didn't change the behavior. I even tried downgrading npm to ^7.7 (npm install [email protected]), and that didn't work either.

Node.js may be ubiquitous, and it might be relatively easy to pick up, but the package management and ecosystem are somewhat cumbersome. Regardless, I do appreciate you looking into it.

[snarkipus]

It's definitely unique to my environment somehow. It's repeatable for me against a dummy hello-world project without any langium dependencies at all. I haven't tested it against the langium environment yet, but downgrading jest and all the associated packages seems to have resolved it for my dummy build. Thanks again for taking a look though @montymxb!

  "dependencies": {
    "@types/jest": "^29.0.0",
    "@types/jest-expect-message": "^1.0.4",
    "@typescript-eslint/eslint-plugin": "^5.28.0",
    "@typescript-eslint/parser": "^5.28.0",
    "eslint": "^8.17.0",
    "eslint-plugin-header": "^3.1.1",
    "jest": "^26.6.3",
    "jest-expect-message": "^1.0.2",
    "npm": "^7.24.2",
    "shx": "^0.3.4",
    "ts-jest": "^26.5.6",
    "ts-node": "^10.9.1",
    "typescript": "^4.7.4"
  }

[montymxb]

No problem! And Interesting, so dropping Jest back down a bit resolved it? Maybe there's something more going on at the low-level, hmm 🤔 . Either way, I'm glad to hear that you were able to resolve it shifting the versions around a bit! I'll keep this in mind, especially if it shows up somewhere else .