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

The width of the timer in the Test Runner is 'jumpy' #6168

Closed
must-git-good opened this issue Jan 15, 2020 · 7 comments · Fixed by #6236
Closed

The width of the timer in the Test Runner is 'jumpy' #6168

must-git-good opened this issue Jan 15, 2020 · 7 comments · Fixed by #6236
Labels
good first issue Good for newcomers pkg/reporter This is due to an issue in the packages/reporter directory type: user experience Improvements needed for UX

Comments

@must-git-good
Copy link

Current behavior:

Currently, the Cypress GUI has a timer that shows during test progress. The current implementation shows the time out to two decimal places, but drops trailing zeroes. So your timer jumps from 10 to 10.53 to 10.8 to 10.92 and then to 11. (As a crude example). This causes the visual space it takes up on the screen to frantically jump around in size. It's a bit dis-concerting.

Desired behavior:

Any visually cleaner implementation. I suggest just showing exactly to two decimal places at all times on the timer. 10 seconds would then be 10.00 seconds. You could also make other adjustments to the sizing of the element container, etc. to help alleviate this as well, but those feel like half measures.

This implementation would still have the element resize, but only at non-frequent, important breaks ( on the # of digit switches)

Test code to reproduce

Run any test suite that takes over 10 seconds to complete. A specific example is not required, as this is a visual UI improvement that should be noticeable for any long-running test.

Versions

Noticed it enough to annoy me at the current version 3.8.x, so not sure if that element has changed or if that changing element has just finally made me roll my eyes enough to open a ticket.

I'd love other suggestions or feedback on whether this bothers anyone else, as well.

@jennifer-shehane
Copy link
Member

Gif of described behavior - note the width of timer elements jumping.

We're open to contributions:

@jennifer-shehane jennifer-shehane changed the title The timer in the Cypress GUI could be more visually friendly. (low priority) The width of the timer in the Test Runner is 'jumpy' Jan 16, 2020
@cypress-bot cypress-bot bot added the stage: ready for work The issue is reproducible and in scope label Jan 16, 2020
@jennifer-shehane jennifer-shehane added pkg/reporter This is due to an issue in the packages/reporter directory type: user experience Improvements needed for UX good first issue Good for newcomers priority: low 🎗 labels Jan 16, 2020
@Manuel-Suarez-Abascal
Copy link
Contributor

@jennifer-shehane @must-git-good I would like to fix this issue. Which solution would you think it'll be the most optimal? Increasing the container's width with CSS or adding or adding two decimals at all times on the timer?

@must-git-good
Copy link
Author

Certainly there are a few approaches, so use your best judgement, but my personal preference would just be to show a consistent set of trailing decimals (probably 2?). But resizing the box itself might be complementary to this effort as well.

Anything that keeps the visuals clean and professional!

@jennifer-shehane
Copy link
Member

@Manuel-Suarez-Abascal We would love an open PR - even one that is a work in progress is fine. I would probably also prefer the 2 decimals always displaying, but if a css solution ends up being better we wouldn't be opposed to that. Check out our contributing doc and ask us if you get stuck.

@Manuel-Suarez-Abascal
Copy link
Contributor

Manuel-Suarez-Abascal commented Jan 23, 2020

@Manuel-Suarez-Abascal We would love an open PR - even one that is a work in progress is fine. I would probably also prefer the 2 decimals always displaying, but if a css solution ends up being better we wouldn't be opposed to that. Check out our contributing doc and ask us if you get stuck.

Hi @jennifer-shehane, I'm trying to push my code changes & open a PR.
However, whenever I try to push the changes I get this error message:

cant-push-code

I might need some help on how to push my code & open a PR for review! Thanks in advance! 🙂

EDIT:

After some investigation, I realized that I might had git clone the original repo & not the forked one. I'll rewrite during this weekend!

@cypress-bot cypress-bot bot added stage: work in progress stage: needs review The PR code is done & tested, needs review and removed stage: ready for work The issue is reproducible and in scope stage: work in progress stage: needs review The PR code is done & tested, needs review labels Jan 24, 2020
@cypress-bot cypress-bot bot added stage: pending release and removed stage: needs review The PR code is done & tested, needs review labels Jan 29, 2020
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Jan 29, 2020

The code for this is done in cypress-io/cypress#6236, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@flotwig
Copy link
Contributor

flotwig commented Feb 6, 2020

Released in 4.0.0.

@cypress-io cypress-io locked as resolved and limited conversation to collaborators Mar 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers pkg/reporter This is due to an issue in the packages/reporter directory type: user experience Improvements needed for UX
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants