-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2e test in latest wepack version not working #1981
Comments
ng e2e gives always succeeded even if you change the test to "api works" for example |
+1 |
I temporarily fixed this issues by rolling back the version of protractor to 3.3.0. Possibly related to this issue angular/protractor#3511 |
but at least the test failed this way (-) can we make jokes (-)? |
@stefanaerts you are right it does not work with protractor 3.03 on a new cli generated app with 1.0.0-beta.11-webpack.8, but my migrated project to 1.0.0-beta.11-webpack.8 this worked for me. I did, however, run a quick test on this newly generated app and updated my protractor to protractor 4.0.5 and it worked. First I deleted my node_modules and did a clean npm install and it started failing my tests I wanted to fail. Not sure why my migrated app is different than a new one? |
what is in your package.json? |
Here is a link to a repo I just pushed to, look at initial commits 1 and 2. https://github.com/duncanhunter/ngrx-demo I took the following steps
|
@Brocco and did a cast in the test.ts: i added more tests to components in separated directories and and test.ts found them all, so the script works fine this way. |
Here's some background: angular/protractor#3505 |
please read christian, its solved |
Like I said, I just wanted to give some background regardless of whether it's solved or not. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
OSX El Capitan
Versions. Please run
ng --version
. If there's nothing outputted, please runin a Terminal:
node --version
and paste the result here:angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: darwin x64
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
created default app and added typescript to the package.json and changed the rxjs version to 5.0.0-beta.06 instead 11
The log given by the failure. Normally this include a stack trace and some
more information.
my package.json:
"name": "temp-app",
"version": "0.0.0",
"license": "MIT",
"angular-cli": {},
"scripts": {
"start": "ng serve",
"lint": "tslint "src/*/.ts"",
"test": "ng test",
"pree2e": "webdriver-manager update",
"e2e": "protractor"
},
"private": true,
"dependencies": {
"@angular/common": "2.0.0-rc.5",
"@angular/compiler": "2.0.0-rc.5",
"@angular/core": "2.0.0-rc.5",
"@angular/forms": "0.3.0",
"@angular/http": "2.0.0-rc.5",
"@angular/platform-browser": "2.0.0-rc.5",
"@angular/platform-browser-dynamic": "2.0.0-rc.5",
"@angular/router": "3.0.0-rc.1",
"core-js": "^2.4.0",
"rxjs": "5.0.0-beta.06",
"ts-helpers": "^1.1.1",
"zone.js": "0.6.12",
"typescript": "2.0.0"
},
"devDependencies": {
"@types/jasmine": "^2.2.30",
"angular-cli": "1.0.0-beta.11-webpack.8",
"codelyzer": "~0.0.26",
"jasmine-core": "2.4.1",
"jasmine-spec-reporter": "2.5.0",
"karma": "0.13.22",
"karma-chrome-launcher": "0.2.3",
"karma-jasmine": "0.3.8",
"karma-remap-istanbul": "^0.2.1",
"protractor": "4.0.3",
"ts-node": "1.2.1",
"tslint": "3.13.0",
"typescript": "2.0.0"
}
}
Mention any other details that might be useful.
ng test works,
ng e2e not, i see in a flits the word "data;" in the browser url bar before it closes.
The text was updated successfully, but these errors were encountered: