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
There is no way to clean out old test run database tables #3868
Comments
The button should be way at the bottom. Isn't it? |
Not always
…On Tue, Jun 25, 2019, 7:35 AM Herb ***@***.***> wrote:
The button should be way at the bottom. Isn't it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3868?email_source=notifications&email_token=AADBER6CJ7TZPNV4PQK34C3P4IULJA5CNFSM4HYOIXU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYQOUBQ#issuecomment-505473542>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADBER433FG43RWWD6NBEKLP4IULJANCNFSM4HYOIXUQ>
.
|
So the problem seems to be that this button is located at the bottom of the "List tests" page ( We have 3 options:
Which one do we want? |
...another point is that we have a "Clear results after each complete test suite run" checkbox in
Which if I am reading things correctly, means that the "Clean test environment" fieldset should not be available when that setting is on. Right? |
Sometimes it does on the test results page (your option 2), but it wasn't in this instance. Maybe we could solve the problem by always adding a link into the message (your option 1) Then we could remove it from this page always (for consistency) and take the mystery out of it. Or, we could do option 3.
Well, in my case the tests failed half way through. I needed the button regardless of the setting. |
Description of the bug
After a test fails half-way through, you get directed to the "error page". On the "error page" you will see a message that says;
But there is no "Clean environment button" provided on the error page.
Steps To Reproduce
To reproduce the behavior:
The text was updated successfully, but these errors were encountered: