Uploaded image for project: 'Qt Safe Renderer'
  1. Qt Safe Renderer
  2. QSR-1024

auto.pro content clarification

    XMLWordPrintable

Details

    • User Story
    • Resolution: Out of scope
    • P2: Important
    • None
    • QSR 2.0
    • Testing
    • None
    • 0.5

    Description

      The configuration space needs a little bit of clarification and perhaps alignment with the full-blown Coin configurations for the QSR.

      https://codereview.qt-project.org/gitweb?p=tqtc-boot2qt/qtsaferenderer.git;a=blob;f=tests/auto/auto.pro;h=ca1161491d260ad8ef230d8e90f40d111437393d;hb=refs/heads/1.2

      Definition of Done

      1. All wanted build and test targets are covered with test cases
      2. Tests are run and pass in all applicable configurations in Coin
      3. Tests are run and pass in all applicable configurations in Jenkins
      4. Test cases are in TestRail suites and plans
      5. Configuration matrix is available in corresponding test plan description in TestRail

      TestRail: Results

        Attachments

          Issue Links

            relates to

            Task - A task that needs to be done. QSR-1017 Check QSR Coin QEMU Linux configs and tst_Bic

            • P4: Low - Would be nice to fix, but it's not very important.
            • Closed

            Suggestion - Public suggestions QSR-1016 Check QEMU autotest modules

            • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
            • Closed

            User Story - Created by Jira Software - do not edit or delete. Issue type for a user story. QSR-1033 Refresh the test suites and plans

            • P2: Important - Urgent, should be fixed, but will not stop the release.
            • Withdrawn

            User Story - Created by Jira Software - do not edit or delete. Issue type for a user story. QSR-1215 Plan test automation architecture

            • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
            • Closed
            mentioned in

            Page Loading...

            Page Loading...

            Activity

              People

                teemu.holappa Teemu Holappa
                assaarel Asmo Saarela
                Veli-Pekka Heinonen Veli-Pekka Heinonen
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases