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

[CLA Approved] test: add e2e test for tracking time conductor history in fixed mode #5906

Conversation

sabrinapowell
Copy link

Closes #5905

Describe your changes:

E2E tests were added for tracking time conductor history in fixed mode. The test updates the start and end times and checks that the time conductor history is also updated.

NB: I am seeing a bug with the feature being tested. When the end time is updated, the history does not always update. The error happens more than half of the times I have tested it.

Testing

To test the changes, run npm run test:e2e:local -- timeConductor.

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Is this change backwards compatible? For example, developers won't need to change how they are calling the API or how they've extended core plugins such as Tables or Plots.

Author Checklist

  • Changes address original issue?
  • Tests included and/or updated with changes?
  • Command line build passes?
  • Has this been smoke tested?
  • Testing instructions included in associated issue OR is this a dependency/testcase change?

Reviewer Checklist

  • Changes appear to address issue?
  • Reviewer has tested changes by following the provided instructions?
  • Changes appear not to be breaking changes?
  • Appropriate automated tests included?
  • Code style and in-line documentation are appropriate?
  • Has associated issue been labelled unverified? (only applicable if this PR closes the issue)
  • Has associated issue been labelled bug? (only applicable if this PR is for a bug fix)

@codecov
Copy link

codecov bot commented Oct 22, 2022

Codecov Report

Merging #5906 (1703f9b) into master (41fc502) will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5906      +/-   ##
==========================================
- Coverage   54.51%   54.49%   -0.02%     
==========================================
  Files         599      599              
  Lines       23331    23331              
  Branches     2080     2080              
==========================================
- Hits        12718    12714       -4     
- Misses      10028    10032       +4     
  Partials      585      585              
Flag Coverage Δ *Carryforward flag
e2e-ci 39.49% <ø> (ø) Carriedforward from 41fc502
e2e-full 51.23% <ø> (ø) Carriedforward from 41fc502
e2e-stable 46.60% <ø> (-1.96%) ⬇️
unit 50.28% <ø> (ø)

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files Coverage Δ
src/plugins/plot/configuration/SeriesCollection.js 61.53% <0.00%> (-6.16%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 41fc502...1703f9b. Read the comment docs.

@unlikelyzero unlikelyzero self-requested a review October 23, 2022 16:39
@unlikelyzero unlikelyzero added this to the 2.1.3 milestone Oct 23, 2022
@unlikelyzero
Copy link
Collaborator

unlikelyzero commented Oct 24, 2022

@sabrinapowell Thank you for this submission. It looks great! I'm going to do a more thorough review this afternoon.

It looks like it's failing in CI. Do you know why that might be? Is it related to the bug you mentioned?

@sabrinapowell
Copy link
Author

@sabrinapowell Thank you for this submission. It looks great! I'm going to do a more thorough review this afternoon.

It looks like it's failing in CI. Do you know why that might be? Is it related to the bug you mentioned?

Right, the bug is causing the test to fail.

@ozyx ozyx added the source:community Community contribution or request label Oct 24, 2022
@sabrinapowell
Copy link
Author

Hi @unlikelyzero, please let me know when you get a chance to check out the bug. In the meantime, I am available to take another task.

@unlikelyzero
Copy link
Collaborator

unlikelyzero commented Oct 28, 2022

Hi @unlikelyzero, please let me know when you get a chance to check out the bug. In the meantime, I am available to take another task.

@sabrinapowell sorry! I'm having git issues due to xcode shenangans and just got this checked out! Let me take a look and get back to you.

It sounds like a legit bug and in that case, we'd want to file and issue and use the .annotation() api to link to.

@unlikelyzero
Copy link
Collaborator

@sabrinapowell There is a timing issue when running at full speed. I've added some logic to the test to wait for menus to collapse. Will push to your branch

@sabrinapowell
Copy link
Author

@unlikelyzero Thanks for looking into it. I'll check out the change once it has been pushed. I also want to write tests for the remaining tests in the file.

@unlikelyzero unlikelyzero removed this from the Target:2.1.3 milestone Nov 15, 2022
@ozyx ozyx changed the title test: add e2e test for tracking time conductor history in fixed mode [CLA Approved] test: add e2e test for tracking time conductor history in fixed mode Nov 21, 2022
@unlikelyzero
Copy link
Collaborator

@sabrinapowell unfortunately, we're going to have to close this PR as we're doing a total rewrite of our time conductor plugin. This is, in part, due to the number of bugs you uncovered when writing these tests! When the rewrite is available, I'll ping you in the discussion :)

If you'd like to move onto another area to tackle, please ping me back in the #4303

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
source:community Community contribution or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

E2E: Time Conductor History tracking
3 participants