Details
-
User Story
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
None
-
None
-
21
Description
In Catch2, I can share common setup code like this:
SCENARIO("....") { ~~~ setup ~~~~ GIVEN(".....") { ~~~ setup ~~~~ WHEN("....") { ~~~~ action ~~~~ THEN("....") { ~~~~ checks ~~~~ } } ~~~ more WHEN ~~~~ } ~~~~ more GIVEN ~~~~ } ~~~~ more SCENARIOs ~~~~
I'd like to do the same with QTestLib instead of having to write JUnit-like test functions.
Like in Catch2, these dynamic section should not only be used in error reporting, but also in test subset selection.
Attachments
Issue Links
- covers
-
QTBUG-123009 Print a "backtrace" from the exception-throwing QTest macros
- Reported