Test execution

      The need to write scripts to determine test plans and execute them (flaky handling) should be minimized (for example, COIN currently runs qmake -r to create a test plan). However, it should be considered what ctest provides, first.

      • Add functionality create test plan and present results
      • Move flaky rerun policies into testlib (note ctest also has some re-run feature)

      Extend functionality

      • Provide more Gui utilities (High DPI screen/window sizes, High DPI fuzz comparison, image comparison); potentially as a separate module? This would allow for removing a lot of code duplicated in the tests.


      • Bring code up to scratch (however carefully considering performance)
      • Check macros:
        • Consider using exceptions instead of void returns - this would remove the need to always use void for helper functions
        • Performance: Restructure QCOMPARE to only format the operands to strings in case of failure (currently, operands are always formatted, which is costly)
        • Provide other operators (QLESS_THAN,...) which allows for removing a lot of QVERIFY and log the values in case of fails
      • Data driven tests
        • Performance: Use coroutines to yield test data via some tuple (would remove the need to store a matrix of QVariants which is a performance hit, currently)
        • Provide something for resources during shared over the live time of data driven tests. This is currently not possible.


          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.



              • Assignee:
                paeglis Gatis Paeglis
                paeglis Gatis Paeglis
              • Votes:
                0 Vote for this issue
                10 Start watching this issue


                • Created:

                  Gerrit Reviews

                  There are no open Gerrit changes