Comments (2)
The karmaTestExplorer.angularProcessCommand
setting is what you need, but should only be given a single command or script file. It will not work if set to a command + argument combination.
So in this case you should create a small script file which launches node with all the relevant arguments you need, and then set angularProcessCommand
to the path of that script file. The extension will replace the node
in the regular test launch command with your script (ie, as if it were the node
command), and pass it all the other arguments that it would otherwise pass to node
for the test.
So the script needs to be able to accept arguments and call node with those arguments while also adding the additional memory arguments that you need.
Usually, this can be a simple #!/bin/bash
or #!/usr/bin/env node
or other type of script.
from karma-test-explorer.
Feel free to reopen if still an issue.
from karma-test-explorer.
Related Issues (20)
- If even 1 test fails, tests fail to load Test discovery failed: Process exited with non-zero status code 1 (Click to show log) HOT 8
- Cannot run new test - Another test operation is still running HOT 1
- Tests not loaded for default generated Angular 15 project HOT 9
- Tests not loaded for default generated Angular 15 workspace - follow up to issue #60 HOT 2
- Getting error Failed to load tests - Karma server failed to start: spawn npx karma ENOENT HOT 2
- Test Explorer not showing all tests when sharding tests HOT 2
- Debug hangs up if a breakpoint is set. HOT 13
- Unable to install extension HOT 2
- Support different browsers when using multiple projects HOT 8
- Failed to load tests - Karma server failed to connect: Browser Failure - cannot start HOT 25
- Can not run in Angular 11 HOT 1
- Cannot use karma.config.local.js HOT 6
- Nx support HOT 10
- Yarn PNP support HOT 1
- High CPU usage - vscode hangs when the extension is loaded HOT 1
- Cannot debug a test multiple times while in a container HOT 13
- Get error Uncaught ReferenceError: global is not defined HOT 1
- Angular debug tests only works first time then breakpoint ignored and then Another test operation is still running error occurs HOT 1
- Karma Test Explorer Fails to Show Tests Angular 8 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from karma-test-explorer.