Replies: 2 comments 1 reply
-
See #236 :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Today another problem arrive :( Microsoft stops support VS Code for Windows 7. Last working version is 1.70.3. Now test suite downloads 1.71.0 and fails to run tests. Solution: explicitly pass VS Code executable path to runTests({
vscodeExecutablePath: './.vscode-test/vscode-win32-archive-1.70.3/Code.exe',
... Can we somehow workaround this problem (do not mess with modified file in Git)? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Branch A
has unit testA
,Branch B
has unit testB
When developer checkout from
Branch A
toBranch B
old test filesA
are present inout
folder and they may produce errors, when launch extension's test viaDebug (Ctrl + Shift + D) -> Test Extension -> F5
.Solution:
npm run pretest
after each branch switching.Add
pretest
tolaunch.json
too expensive, we need quick test, not full recompile each time.Maybe we need add some info about this to
Contibution.md
, for such newbie developers like me :) ? I can't write it in clean way, I'm terrible in this. Can you @mark-wiemer ?Why
tsc
inwatch
mode don't detect missing files and not delete correspondingjs
files?Beta Was this translation helpful? Give feedback.
All reactions