-
Notifications
You must be signed in to change notification settings - Fork 24
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
Make it possible to look for a domain history without running a test #333
Conversation
Of course, since the GUI has evolved, the tests are breaking. This makes me think, I haven't created any tests for this feature. I'll provide some. |
Will "Check" and "History", respectively, really be understandable? What about "Run a new test" and "View completed tests"? |
Well, I disagree. Especially "history" I find problematic.
From the screen shot I do not think the number of words is a problem. Technically, it could sometimes be the latest test. So "Check" and "View completed tests" then? |
I think we are trying to address something with a very subjective point of view. During F2F we decided to do some deep work on the GUI in 2023/2024. Hopefully this would be done with the help from UX/UI experts. In the meantime I find it hard to come up with the best wording. |
Now the interface is quite simple. There is one field to fill in and one button to press. The exact wording on that button is less important because there is no choice. With this change there will be two buttons to choose between, and suddenly it is important what the buttons say, and maybe the color, to make sure that the interface does not get too complex. What do you think of adding a radio button under "Options" under "o Disable IPv4"? E.g.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really think that moving the feature done to the options section is the correct approach. The feature will not be used very much, and therefore it should not increase the complexity of the interface for the common usage.
The radio button is a bad approach in my opinion, viewing the test history is not an parameter for the test but a completely different action. I do think though that the wording should be improved, I propose On a side note the option form is only used for testing a domain, I think the wording there should also be changed, e.g. |
I think you have a point. First I reacted on the wording, then I felt that the alternative of viewing test history came too much in focus. Today, you fill the domain in and press the only button there is. With the proposed change, you have to decide which of the two buttons to press, which is increased complexity for the newcomer or seldom-comer. That is why I suggested a radiobutton (or could be a check box) in the options section. I requested the feature, but I do not expect it to be used very much. That will not be the common action. It should not take the focus from the main action, to run a test.
What about keeping the check button as is, and adding a check box under the domain field with some text saying that a new check should not be run, only give a list of completed tests.
I agree that "Test options" would be better than today's "options". |
I am not sure about that. If we want to keep this form straightforward and simple what about adding a page "History" accessible from the navigation menu that is just about looking up hold tests for a domain name? Typically I see this to be like the proposed "History" page screenshot but with a input and button bellow the title page. Like this we would also avoid having to go back to look up another domain and we avoid confusion between the two feature. |
And adapt e2e tests.
* move code into new method * move sanitizeDomain() to a new utils file
A fluid container uses the whole width, the default container is limited to a maximum width, which is big enough when it comes to the modal preview of the history. The modal width is smaller than the max-width of the container class.
The "row" class adds some negative margin left and right, which breaks the alignment when the history is not rendered in a modal window. The default behavior to this point was to display the history in a modal window. With this work, the history will also be available on its own. Therefore some adjustments in the rendering is needed.
And fix e2e tests to make them pass.
A Backend connection error is different from an error because of a malformed domain name.
Reuse the progress bar fully charged to let the user know that its request is being processed. The bar is full since we can't have an easy access to the remaining time to process the query.
Otherwise previous results remain, and the error message can't be displayed.
I moved the feature to another page "History" accessible from the navigation menu. |
I recall that when discussing about this PR, there was a suggestion to use a different color for the History button. But I might have missed something.
This is a good idea, I've open #338 for that, so that this PR focuses on this new history feature. |
When both were in the same tab it might have made sense, but when they are in different tabs it is better to have a uniform look and feel.
That is reasonable. |
Purpose
This PR is about providing an easy way to fetch previous results for a given domain.
A new page has been created that provides a form similar to the domain check's form to look for a test's history. The history list is displayed on the page reusing the modal (from the result page).
Two new routes are created:
/history
that displays the page with the history form/history/<domain>
that populates the form and queries for the history of <domain>.Context
Addresses #309
Changes
/history
/history/<domain>
sanitizeDomain()
method from the form component has been moved to an external file to make it available to the project (expand this method to convert the domain to lower case)How to test this PR
Open the History page. Here is a list of things that can be tested:
/history/<domain>
Old proposal
1. Display a secondary button
Screenshots