Loading...

XML

Word

Printable

Maintaining RTA with current style is quite challenging and for example results analysis requires too much manual effort.

Requirements (generate sub-tasks for these):

No need for RTA team to read results. Release Manager or basically anybody should be able to see if tests were OK. Task id: https://bugreports.qt.io/browse/QTQAINFRA-2240
Test environment configuration management
- Changes in CI does not break RTA. Task id: https://bugreports.qt.io/browse/QTQAINFRA-2093
- Updating CI configurations should match RTA configurations. Task id: https://bugreports.qt.io/browse/QTQAINFRA-2329
Simplifying RTA test structure, task id: https://bugreports.qt.io/browse/QTQAINFRA-2334
Backwards compatibility, task id: https://bugreports.qt.io/browse/QTQAINFRA-2330 (branching & tagging)

Test results, suite, test case documentation, task id: https://bugreports.qt.io/browse/QTQAINFRA-2331

- Static test results are needed, hide sensitive data from RTA logs, task id: https://bugreports.qt.io/browse/QTQAINFRA-2332
- Automatic...no need to update for example wiki pages
- Result presentation...also for partners
UI example for each module: https://bugreports.qt.io/browse/QTQAINFRA-2336

relates to

QTQAINFRA-2336 Create detailed UI tests for one example application/ Qt module

QTQAINFRA-2240 Investigate TestRail/TeamServer

QTQAINFRA-2329 Define process for adding new configuration to RTA

QTQAINFRA-2330 Investigate the pros and cons of branching RTA test code

QTQAINFRA-2331 Create documentation for RTA test code

QTQAINFRA-2334 Define RTA requirements

(1 relates to)

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

There are no open Gerrit changes