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

Keep "specs list tree" state (scroll position, open / closed folders, ...) #29255

Open
luis-pato opened this issue Apr 3, 2024 · 2 comments
Open
Labels
type: enhancement Requested enhancement of existing feature type: user experience Improvements needed for UX

Comments

@luis-pato
Copy link

What would you like?

I have a project with many components and many tests, so that "test list" on the left side is quite long.

Whenever the tests find an error and i fix my code, after clicking SAVE on the code editor, the tests run again. This is great and a really nice UX.
The problem is that the "specs list tree" (i mean that bar with this the folders and tests tree on the left side of the window, with the tests list) always scrolls back to the top and any closed folders are now again open. So each time i have to at least scroll back down.

cypressCapture_small
(Notice how each time i change the test code the file tree scrolls back to the top and all folders are open again)

I think it would be great if this "specs list tree" could keep track of the state. At least for things like scroll position, closed / open state of folders.

Why is this needed?

The tests work well without this feature, but having it would save some time and make the user experience much better. And maybe even prevent some small error when components / test suits have similar names

Other

I am running Cypress 13.7.1 on a mac with MacOS Sonoma 14.1.1.
I am running the tests in a chrome window (123.0.6213.105.

Let me know if you need any other information...

@jennifer-shehane jennifer-shehane added type: user experience Improvements needed for UX type: feature New feature that does not currently exist type: enhancement Requested enhancement of existing feature and removed type: feature New feature that does not currently exist labels Apr 3, 2024
@jennifer-shehane
Copy link
Member

I can definitely see how this is annoying. We don't have any work planned around this area of code anything soon, but I'll leave this open as an enhancement to be considered.

@luis-pato
Copy link
Author

I can definitely see how this is annoying. We don't have any work planned around this area of code anything soon, but I'll leave this open as an enhancement to be considered.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Requested enhancement of existing feature type: user experience Improvements needed for UX
Projects
None yet
Development

No branches or pull requests

2 participants