Skip to content
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 Tests incorrect in default project #1977

Closed
PooperPig opened this issue Sep 5, 2016 · 5 comments · Fixed by #2054
Closed

E2E Tests incorrect in default project #1977

PooperPig opened this issue Sep 5, 2016 · 5 comments · Fixed by #2054

Comments

@PooperPig
Copy link

  1. El Capitan
  2. bash-3.2$ ng --version
    Could not start watchman; falling back to NodeWatcher for file system events.
    Visit http://ember-cli.com/user-guide/#watchman for more info.
    angular-cli: 1.0.0-beta.11-webpack.8
    node: 6.5.0
    os: darwin x64
  3. Create an app using ng new
    change the e2e test from
  it('should display message saying app works', () => {
    page.navigateTo();
    expect(page.getParagraphText()).toEqual('app works!');
  });

to

  it('should **NOT** display message saying app works', () => {
    page.navigateTo();
    expect(page.getParagraphText()).toEqual('app **doesnt** works!');
  });

then run ng e2e
output is:
`bash-3.2$ ng e2e                                                                                
Could not start watchman; falling back to NodeWatcher for file system events.                   
Visit http://ember-cli.com/user-guide/#watchman for more info.                                  
                                                                                                

 [email protected] pree2e /Users/pooperpig/projects/Angular 2 Projects/cliTest                        
 webdriver-manager update                                                                      
                                                                                                
[13:56:58] I/update - chromedriver: file exists /Users/pooperpig/projects/Angular 2 Projects/cliTest
/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedriver_2.22mac32.zip     
[13:56:58] I/update - chromedriver: unzipping chromedriver_2.22mac32.zip                        
[13:56:58] I/update - chromedriver: setting permissions to 0755 for /Users/pooperpig/projects/Angula
r 2 Projects/cliTest/node_modules/protractor/node_modules/webdriver-manager/selenium/chromedrive
r_2.22                                                                                          
[13:56:58] I/update - chromedriver: v2.22 up to date                                            
[13:56:58] I/update - selenium standalone: file exists /Users/pooperpig/projects/Angular 2 Projects/
cliTest/node_modules/protractor/node_modules/webdriver-manager/selenium/selenium-server-standalo
ne-2.53.1.jar                                                                                   
[13:56:58] I/update - selenium standalone: v2.53.1 up to date                                   
                                                                                                
 [email protected] e2e /Users/pooperpig/projects/Angular 2 Projects/cliTest                           
 protractor "./protractor.conf.js"                                                             
                                                                                                
[13:56:59] I/direct - Using ChromeDriver directly...                                            
[13:56:59] I/launcher - Running 1 instances of WebDriver                                        
Spec started                                                                                    
                                                                                                
  cli-test App                                                                                  
    ✓ should NOT display message saying app works                                               
                                                                                                
Executed 1 of 1 spec SUCCESS in 0.02 sec.                                                       
[13:57:00] I/launcher - 0 instance(s) of WebDriver still running                                
[13:57:00] I/launcher - chrome #1 passed                                                       
                                                                                                
All end-to-end tests pass.         `

  1. Whatever I try, I cannot get the test to fail!
  2. I have tried ngBuild in between changes etc. The text of the test changes ( so it is picking up the changed source) but the tests themselves don't fail.

Appreciate this isn't necessarily an angular-cli issue per se, but its my first port of call!


Thanks! We'll be in touch soon.

@stefanaerts
Copy link

for me the same. i am using the webpack 1.0.0-beta.11-webpack.8 version.
ng test works
ng e2e does not work, i see in a flits the word data; in the browser url bar and then i always get the result test passed.

@evanrooijen
Copy link

+1

@ghost
Copy link

ghost commented Sep 9, 2016

angular/protractor#3505

@stefanaerts
Copy link

#1981 (comment)

On Mon, Sep 12, 2016 at 5:30 AM, Hans [email protected] wrote:

Closed #1977 #1977 via
#2054 #2054.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#1977 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADg493DOcXnp5geL5XoLia_bYrUApxQoks5qpMdMgaJpZM4J0uXX
.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants