-
Notifications
You must be signed in to change notification settings - Fork 4
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
[serialization] Layout for when write
test results are available
#44
Comments
izzyreal
changed the title
[serialization] Layout for when
[serialization] Layout for when Jul 30, 2023
specwrite
test results are availablewrite
test results are available
generalmimon
added a commit
that referenced
this issue
Aug 5, 2023
generalmimon
added a commit
that referenced
this issue
Aug 5, 2023
generalmimon
added a commit
that referenced
this issue
Sep 17, 2023
generalmimon
added a commit
that referenced
this issue
Oct 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe I could do some preliminary work on integrating
write
test results. If the prospective API is already known, that would be nice to have, but much of the other requirements can already be taken care of.What kind of layout do you have in mind?
Some ideas:
Make it one big page where the current content is repeated once below it, populated withwrite
results. Both content chunks would have a header. Simple UI change but lots of scrolling required for those who want to seewrite
.Same layout as now, but with a button to toggle betweenread
andwrite
view.read only
,write only
,read and write
views.We may want to anticipate if the current sorting by name would work out favorably, and yields easily identifiable pairs on the screen for tests where both both read and write tests exists. If it is indeed valuable to be aware of such pairs, we may even want to think about visual emphasis, like giving the testname fields a distinct background color.
Update: ideas 1. and 2. are off the table because @GreyCat already mentioned separate and aggregated view for reading and writing tests on Gitter.
The text was updated successfully, but these errors were encountered: