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 test not reflecting changes to component unless restarted #2642

Closed
kensodemann opened this issue Aug 18, 2020 · 1 comment
Closed

e2e test not reflecting changes to component unless restarted #2642

kensodemann opened this issue Aug 18, 2020 · 1 comment
Labels

Comments

@kensodemann
Copy link
Member

Stencil version:

 @stencil/core@1.17.3

I'm submitting a:

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://stencil-worldwide.herokuapp.com/ or https://forum.ionicframework.com/

Current behavior:

When running stencil test --spec --e2e --watchAll, changes to components that should cause e2e testing failures are not picked up. The test needs to be restarted in order to show the failure.

Steps to reproduce (at the moment)

Expected behavior:
Changes to components would be picked up by the e2e test with

Steps to reproduce:

I am working on getting a repro case from the community member reporting this. The original repro case is no longer available.

Essentially, however:

  1. stencil test --spec --e2e --watchAll
  2. edit a component to make changes that would break an e2e test involving that component
  3. a rebuild occurs and the tests run, but no tests are broken
  4. shut-down and restart the tests, now the proper tests are broken
  5. undo edit to component
  6. a rebuild occurs and the tests run, but the same tests are broken even though the code is now fixed
  7. shut-down and restart the tests, now the tests are back to being successful

It is as if the e2e test is caching an older version of the component or something.

@ionitron-bot ionitron-bot bot added the triage label Aug 18, 2020
@kensodemann kensodemann changed the title e2e test not e2e test not reflecting changes to component unless restarted Aug 18, 2020
@kensodemann
Copy link
Member Author

Here is a repro case for this one: https://github.com/jcfranco/stencil-test-watch-not-picking-up-component-updates

Repro steps (also in e2e test):

  1. run npm run test.watch my-component.e2e
  2. wait for initial test run
  3. keeping test watcher on, change my-component#test to something else and save
  4. test will run again and pass (it should fail)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant