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 have my testcafe installation local for context.
I originally had my testcafe path as blank in settings, and I was able to debug just fine, however when I went to just run them, the testcafe.js file would just open in another vscode window and wouldn't actually run the tests.
To combat this I tried manually specifying the path myself, and when I ran it, it appended package.json to the path and complained it did not exist. Come to find out if I just do the parent folder (No bin/testcafe.js) it works just fine.
Not sure why that is happening for me and not others, but my configuration is using the typescript setup (So esm) and my tests folder is called "e2e" instead
The text was updated successfully, but these errors were encountered:
I have my testcafe installation local for context.
I originally had my testcafe path as blank in settings, and I was able to debug just fine, however when I went to just run them, the testcafe.js file would just open in another vscode window and wouldn't actually run the tests.
To combat this I tried manually specifying the path myself, and when I ran it, it appended package.json to the path and complained it did not exist. Come to find out if I just do the parent folder (No bin/testcafe.js) it works just fine.
Not sure why that is happening for me and not others, but my configuration is using the typescript setup (So esm) and my tests folder is called "e2e" instead
The text was updated successfully, but these errors were encountered: