ChatGPT解决这个技术问题 Extra ChatGPT

Running a single test file

Is there a way to run ng test for a single file instead of for the entire test suite? Ideally, I'd like to get the quickest possible feedback loop when I'm editing a file, but karma executes the whole suite on each save, which is a bit slow when you build up a big enough test suite.

This is different from How to execute only one test spec with angular-cli in that that question is about running an individual spec. This is about running an individual file. The solution involves the same Jasmine spec feature, but the nature of the question is slightly different.

You can find an answer here: stackoverflow.com/questions/40683673/…
You can find an answer here: stackoverflow.com/questions/40683673/…
I believe this is the best answer to this question now that angular has added glob matching via the include param stackoverflow.com/a/59723121/2002095

M
MAbraham1

I discovered that Jasmine allows you to prefix describe and it methods with an f (for focus): fdescribe and fit. If you use either of these, Karma will only run the relevant tests. To focus the current file, you can just take the top level describe and change it to fdescribe. If you use Jasmine prior to version 2.1, the focusing keywords are: iit and ddescribe.

This example code runs just the first test:

// Jasmine versions >/=2.1 use 'fdescribe'; versions <2.1 use 'ddescribe'
fdescribe('MySpec1', function () {
    it('should do something', function () {
        // ...
    });
});

describe('MyOtherSpec', function () {
    it('should do something else', function () {
        // ...
    });
});

Here is the Jasmine documentation on Focusing Specs, and here is a related SO article that provides additional thoughtful solutions.


legendary answer
Can't believe such important functionality is not more obvious and straightforward.
it works but it is not ideal because you need to change the source code and you can end up checking in the modified code in source control.
Please add links to official documentation, when possible
Ok fdescribe is one option. But what about if project has 100spec files? And you want to run just one spec file? ng test compile all files...
L
Levi

This can be achieved these days via the include option. https://angular.io/cli/test#options

It's a glob match, so as an example:

ng test --include='**/someFolder/*.spec.ts'

I can't find it in the 8.1.0 release notes, but @Swoox mentions below this is a feature after cli version 8.1.0. Thanks for figuring that out.


This seems like a recent update. Might want to include what version is needed. CLI 8.1 is needed.
Seems to be removed in v9.1 :(
I just tested this in CLI v9.1.0 and it works perfectly.
Works in CLI v10.0.4 too
Works with CLI v12
D
DiPix

It's worth mentioning that you can disable particular test without commenting by xdescribe and xit

xdescribe('Hello world', () => { 
  xit('says hello', () => { 
    expect(helloWorld())
        .toEqual('Hello world!');
  });
});

And as somebody already said if you want to focus on some test then fdescribe and fit

fdescribe('Hello world', () => { 
  fit('says hello', () => { 
    expect(helloWorld())
        .toEqual('Hello world!');
  });
});

v
var-bin

I found that ng test has an additional option --include which you can use in order to be able to run test for a single file, or for a particular directory, or for a bunch of files:

// one file
npm run test -- --include src/app/components/component/component-name.component.spec.ts

// directory or bunch of files
npm run test -- --include src/app/components

ng cli docs


Angular 9 - it seems to have been removed
No, it's still available in NG 9.
R
Roman Mahotskyi

You can go to src/test.ts and can change the following line:

const context = require.context('./', true, /\.spec\.ts$/);

to

const context = require.context('./', true, /**yourcomponent.component**\.spec\.ts$/);

https://i.stack.imgur.com/Dz02U.png


Strictly speaking, this sounds like the most correct answer even though most questions on how to do this have the problem solved by using fit and fdescribe. There is a git issue to accomplish this more easily in Karma: github.com/karma-runner/karma/issues/1507. Ideally, though not simply, we could configure Karma so we could make changes to one test, and then just click on it in the browser to rerun it with the update.
J
Joel Kesler

In Angular 9 I have had luck with the following:

If you want to test a specific file:

ng test --test-file=path/to/your/file.component.spec.ts

If you have multiple projects in your Angular project and/or are using NX, you can specify an Angular project to test:

ng test project-name

You can also use

ng test --testNamePattern componentname

for something like path/to/your/component/componentname.spec.ts. This will scan every file in every project, and is slower.

If you want to test only what has changed since your last commit (using git or other version control)

ng test --only-changed

Not working in vanilla Angular.


I tried to use --only-changed But it is showing an Invalid option, I have gone through the Angular documentation and there is no such option defined. Could you please add some dummy project where it is working?
--Only-changed does not exist in angular cli, please provide reference to angular source and documentation providing this feature
Does ng test -- --only-changed work for either of you? We use NX for our Angular mono-repo, and it may have modified the ng commands. We are also using testing library with angular, which may have also changed things.
T
Tomerikoo

Visual Studio Code Extension

The easiest way is to use the vscode-test-explorer extension along with its child angular-karma-test-explorer and jasmine-test-adapter, you'll get a list of current test to run one by one if you want:

https://i.stack.imgur.com/bmhQt.png

This is the same answer I gave at this question, there's some more details there.


T
Tomerikoo

Using

ng test --main file.spec.ts

K
Kalana

You must have to go src/test.ts and can change the following line number code 18:

//Then we find all the tests.
const context = require.context('./', true, /\.spec\.ts$/);

to

//Then we find all the tests.
const context = require.context('./', true, /testing.component\.spec\.ts$/);

https://i.stack.imgur.com/W15aT.png


H
Hannes Schneidermayer

Why make it so hard?

run ng test

Open the link shown in the console:

https://i.stack.imgur.com/sNGxe.png

On the top right, click on Debug:

https://i.stack.imgur.com/VECZm.png

Click on the test you want to solo run:

https://i.stack.imgur.com/X0Q2z.png

To re-run the test, refresh the browser window (e.g. with F5).


T
Tyler2P

Get the relative path for your test file & provide like this

ng test --include=src\app\app.component.spec.ts

It works for me!!


c
cigien

I was looking for the answer. Your question thread did help me a lot. But, Some point was ambiguous. Especially, If you run the below CLI command.

npm run test -- --include src/app/component/your.component.spec.ts

It will run the single test file, but after running the test, the test browser will be closed immediately, you can't watch your test file due to the missing watch flag. Therefore you have to provide the watch flag as true value. I figured it out that the below CLI command is working fine with the watch flag.

ng test --watch=true "--include" "src/app/components/your.component.spec.ts"

T
Tony

If you are using IntelliJ IDE you can install the ' Karma ' plugin and run specs individually by clicking the ' run ' icon next to the spec test

https://i.stack.imgur.com/2KUsE.png


T
Tomerikoo

Works if you specify your spec file as parameter.

For example:

ng test foo.spec.ts

Can you specify which version are you using? Not working with 1.7.x
It did not work as is for me either. But I modified it to work with the --main option before the path to the spec file. I used an absolute path with forward slashes. Have not tried a relative path. Using Angular 6. Not sure if it is the best solution, but it seems to work for me.

关注公众号,不定期副业成功案例分享
Follow WeChat

Success story sharing

Want to stay one step ahead of the latest teleworks?

Subscribe Now