-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
experiment with the effect of different terminal widths on the test result and testing in general #11433
Comments
I'm happy to submit a PR for this 👍 |
Please give it a go |
For initial characterization I ran the test suite and logged its output for all column values between 40 and 400 which produced the following result
It seems only a small handful of tests are affected which appear to be the same that were identified in #11423 I recommend we refactor these offending tests to be agnostic to the column size -- which I'm happy to do 🙂 It also might be nice to add a test which runs the suite with a subset of different column values to preserve this behavior, however maybe this should exist within CI only as it will take longer to complete. Thoughts? |
After evaluating the failed tests, I added the following test case to
Seems like a bug within the |
That particular line match test should indeed fail, The match asks for 2 lines,one is given |
I suppose? With |
when we took note that certain terminal widths affect the testing, we just configured a default for the full test suite
however this demonstrated that we have a blind spot there
we really need to get a idea what happens to the tests/ux in general when the width is either too small or too big
initial experiments could just vary COLUMNS to identify the areas where things may go south - once pinpointed exact tests an be added
Originally posted by @RonnyPfannschmidt in #11425 (comment)
The text was updated successfully, but these errors were encountered: