After return original code without transpiling, there is error 'Cannot implicitly resolve the test run in the context of which the test controller action should be executed. Use test function's 't' argument instead.'

[IssacH]

Hi @miherlosev @AndreyBelym @pavelgruba @kirovboris @benmonro

I tried to change the code a little bit under compiler.js

In the _compileCode function, the return value will be 'compiled.code'. And when I tried to change the return value with 'code', and then I started my test specs, there will be error 'Cannot implicitly resolve the test run in the context of which the test controller action should be executed. Use test function's 't' argument instead.' Is there any workaround to bypass this? Since I was trying not to use babel to transpile the async/await code.

Thanks,
Issac

[wentwrong]

TestCafe requires test code to be transpiled in order to operate properly, so omitting the compilation phase breaks things. Currently, there is no workaround for showing stack traces in the origin Node.js format or skipping transpiling of async/await code - these are limitations based on how TestCafe works internally. Please use #6067 to track our progress with async stack traces.