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
I'm currently working with a client who's migrating from mocha over to jest. They've gotten used to using context in mocha (which is just an alias for describe) to structure their tests.
So, in their codebase, I'm simply aliasing context to describe, as suggested in this thread: jestjs/jest#2468
However, I'm running into some problems with the runner because it's not looking for context (just describe)
I was looking into this today and realized that this would need to be supported in jest-editor-support, I think. I opened jest-community/jest-editor-support#73 to track that.
I'm currently working with a client who's migrating from
mocha
over tojest
. They've gotten used to usingcontext
inmocha
(which is just an alias fordescribe
) to structure their tests.So, in their codebase, I'm simply aliasing
context
todescribe
, as suggested in this thread: jestjs/jest#2468However, I'm running into some problems with the runner because it's not looking for
context
(justdescribe
)vscode-jest-runner/src/util.ts
Lines 18 to 25 in 65ec6c3
It would be nice if I could configure the plugin to look for
describe
as well ascontext
when generating the targetted test name.The text was updated successfully, but these errors were encountered: