Open maks187 opened 6 years ago
You have wrong specs
path in your protractor configuration file
. You should set path where you store *.js
files. In your case it will be something like ../src/main/typescript/e2e/**/*.e2e-spec.js
but my e2e-spec-file is an ts file:
import { AppMainPage } from './app.po';
describe('App', () => {
let page: AppMainPage;
beforeEach(() => {
page = new AppMainPage();
});
it('plugin mod/com should exist', () => {
page.navigateTo();
expect<any>(page.getModElement()).toBeDefined();
});
// following tests.. it(...); ...
});
yes, I understand.
firstly typescript compiles to javascript, and then javascript files run.
You could read about "outDir": "out-tsc/e2e"
in your tsconfig.
So, in the protractor config file you should type a location of tests that have been already compile into js
Bug report
Node Version:
v8.9.3
Protractor Version:
Version 5.2.2
Angular Version:
5.2.0
Browser(s):
Chrome
Operating System and Version
Windows 10
Description:
doesn't run. it would be ok if the tests doesn't succeed, but when you point out that files are missing from compilation, WHY you don't say WHICH one it is and WHERE (the file-path) it is. How I suppose to know, how your framework is working under the hood? I'm only a user of it, not a developer. A compiler or framework has ALWAYS to point to the error, or it is completely useless!
ng e2e