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

support for reporting multiple executions of the same test in a single run #1

Open
signed opened this issue Mar 27, 2022 · 5 comments

Comments

@signed
Copy link
Contributor

signed commented Mar 27, 2022

Is this something you want to consider?
I know this feature from TestCafe

@stolp
Copy link

stolp commented May 24, 2022

I consider support for this as mandatory.

@marcphilipp
Copy link
Member

@signed @stolp Could you please elaborate?

Would this be multiple executions of a test framework or multiple runs of the same test within the same execution?

If the former, could this be represented by having multiple report files?

If the latter, is there a limitation in the current format that makes representing reruns impossible?

@mmichaelis
Copy link

Quoting TestCafe as referenced by @signed:

Quarantine Mode

Enable quarantine mode to eliminate false negatives and detect unstable tests. When a test fails, TestCafe quarantines it and repeats it until the test yields conclusive results.

This pattern in my experience quite typical for system and especially UI tests. Instead of failing after the first run, you give some "grace" to the test to repeat. And this applies to every single test.

In the end, you want to know:

  • Has there been a successful execution?

    For TestCafe, it seems to be some "ratio" to configure. For us, it is, that the test is only repeated if failing, and only repeated a given number of times, in which it needs to be successful once.

  • Did the test fail at all?

    Unstable tests are expensive (runtime) and may signal an instability of the AUT as well as of the test, which we may want to address at some time. Thus, at least we want to know if we have any tests which required such repetition and see, if we can do better (use a better Wait-Pattern in test or fix unstable AUT).

    For this, we need to have as much information as possible. Especially unstable/flaky tests are hard to debug locally, quite often (Heisenberg Bug). Thus, we collect not only logs of the tests, but, if feasible, also of the AUT (JConsole log, Server log) as well as screenshots.

Does this answer your question, @marcphilipp?

@mpkorstanje
Copy link

@mmichaelis the result element is open for extension. Would you be able to include the additional information about the separate executions of a test there?

https://github.com/ota4j-team/open-test-reporting/blob/main/schema/src/main/resources/org/opentest4j/reporting/schema/core.xsd#L78

@stolp
Copy link

stolp commented Jul 21, 2022

@marcphilipp: I was referring to the latter, multiple runs of the same test in a single test execution.

Regarding your question, I have no idea if this is possible in the current format as I have not yet used it.

I was simply deducting this as a fact from the issue heading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants