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
Here my "test.ts" file that I refer in "karma.conf.js"
// This file is required by karma.conf.js and loads recursively all the .spec and framework files
import 'core-js/es6';
import 'core-js/es7/reflect';
import 'zone.js/dist/zone';
import 'zone.js/dist/long-stack-trace-zone';
import 'zone.js/dist/proxy.js';
import 'zone.js/dist/sync-test';
import 'zone.js/dist/jasmine-patch';
import 'zone.js/dist/async-test';
import 'zone.js/dist/fake-async-test';
import { getTestBed } from '@angular/core/testing';
import {
BrowserDynamicTestingModule,
platformBrowserDynamicTesting
} from '@angular/platform-browser-dynamic/testing';
import './polyfills';
// Built by the core Angular team for mocking dependencies
import 'angular-mocks';
// Unfortunately there's no typing for the `__karma__` variable. Just declare it as any.
declare var __karma__: any;
declare var require: any;
// Prevent Karma from running prematurely.
__karma__.loaded = function () {
};
// First, initialize the Angular testing environment.
getTestBed().initTestEnvironment(
BrowserDynamicTestingModule,
platformBrowserDynamicTesting()
);
// Then we find all the tests.
const context = require.context('./', true, /\.spec\.ts$/);
// And load the modules.
context.keys().map(context);
// Finally, start Karma to run the tests.
__karma__.start();
You are excluding your test.ts and all yours spec files on your tsconfig, maybe you need to use a tsconfig for running your tests, extending that tsconfig and including your test.ts and all specs.
Expected behaviour
Should execute tests - there is 300 + test case in my pro.
Actual behaviour
Throwing an exception Can't execute tests - Executed 0 of 0 ERROR (0.005 secs / 0 secs)
Environment Details
karma --version
):karma.config.js
fileHere my "test.ts" file that I refer in "karma.conf.js"
And this is tsconfig.json
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: