'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.

Solution 1:^[1]

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.

Solution 2:^[2]

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.

Solution 3:^[3]

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!');
  });
});

Solution 4:^[4]

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

Solution 5:^[5]

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

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

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

Solution 6:^[6]

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.

Solution 7:^[7]

Using

ng test --main file.spec.ts

Solution 8:^[8]

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:

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

Solution 9:^[9]

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$/);

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

Solution 10:^[10]

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"

Solution 11:^[11]

Why make it so hard?

run ng test
Open the link shown in the console:

On the top right, click on Debug:

Click on the test you want to solo run:

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

Solution 12:^[12]

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

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	MAbraham1
Solution 2
Solution 3	DiPix
Solution 4	var-bin
Solution 5	Roman Mahotskyi
Solution 6
Solution 7	Tomerikoo
Solution 8	Tomerikoo
Solution 9	Kalana
Solution 10	cigien
Solution 11	Hannes Schneidermayer
Solution 12	Tony

'Running a single test file

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]