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

"History" tab does not refresh when doing consecutive tests #412

Open
tgreenx opened this issue May 9, 2023 · 0 comments
Open

"History" tab does not refresh when doing consecutive tests #412

tgreenx opened this issue May 9, 2023 · 0 comments
Labels
T-Bug Type: Bug in software or error in test case description
Milestone

Comments

@tgreenx
Copy link
Contributor

tgreenx commented May 9, 2023

After running a test on GUI (/run-test), the user gets redirect to a /result/ page at the end of the test, in which the test panel from the /run-test page is still present. This allows the user to quickly re-do a test if desired. However, when doing so, the "History" tab on the /result/ page does not refresh, meaning that it will keep containing the history of tests for the first tested domain.

Steps to reproduce:

  1. Start a test for any domain ("domain1") from the /run-test page.
  2. Wait for the test to complete, after which you are redirected to a /result/ page.
  3. Click on the "History" tab, and check that the completed tests are for "domain1".
  4. Start a new test for another domain ("domain2") from the current /result/ page.
  5. Wait for the test to complete. When the page updates, click on the "History" tab. The list of completed tests will be the same as before (i.e., regarding "domain1"), but it should not (- it should be "domain2").
@tgreenx tgreenx added the T-Bug Type: Bug in software or error in test case description label May 9, 2023
@tgreenx tgreenx added this to the v2023.2 milestone May 9, 2023
@matsduf matsduf modified the milestones: v2023.2, v2024.1 Mar 19, 2024
@matsduf matsduf modified the milestones: v2024.1, v2024.2 Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Bug Type: Bug in software or error in test case description
Projects
None yet
Development

No branches or pull requests

2 participants