Change Details

Teamcity is relying on the test suite name extracted from the JUnit XML report to display display the suite and its tests. This test suite name is hardcoded, so Teamcity treats all the functional test runs as a single one, preventing from accessing the test details from the web UI. This diff adds an option to `test_runner.py` to allow for setting a name for the test suite, and use it to reflect the intent of the runs. **Teamcity UI before this diff (the `test_runner.py` script is invoked twice on this build)** [[ https://build.bitcoinabc.org/viewLog.html?buildId=25239&buildTypeId=BitcoinABC_BitcoinAbcStaging&tab=buildResultsDiv&guest=1 | Link to the example build]] {F4153505} //The UI show 110 tests instead of 220.// {F4153507} //The tests appear only once, despite they are run twice.// **Teamcity UI after this diff** [[ https://build.bitcoinabc.org/viewLog.html?buildId=25998&buildTypeId=BitcoinABC_BitcoinAbcStaging&tab=buildResultsDiv&guest=1 | Link to the example build]] {F4153529} //The UI shows 220 tests as expected.// {F4153511} //The tests appear twice, one for each run. Each test for each run can be accessed directly by clicking the {icon caret-down} next to the test name and select `Show in Build Log`//

Teamcity is relying on the test suite name extracted from the JUnit XML report to display display the suite and its tests. This test suite name is hardcoded, so Teamcity treats all the functional test runs as a single one, preventing from accessing the test details from the web UI. This diff adds an option to `test_runner.py` to allow for setting a name for the test suite, and use it to reflect the intent of the runs. **Teamcity UI before this diff (the `test_runner.py` script is invoked twice on this build)** [[ https://build.bitcoinabc.org/viewLog.html?buildId=25239&buildTypeId=BitcoinABC_BitcoinAbcStaging&tab=buildResultsDiv&guest=1 | Link to the example build]] {F4153505} //The UI show 110 tests instead of 220.// {F4153507} //The tests appear only once, despite they are run twice.// **Teamcity UI after this diff** [[ https://build.bitcoinabc.org/viewLog.html?buildId=26862&buildTypeId=BitcoinABC_BitcoinAbcStaging&tab=buildResultsDiv&guest=1 | Link to the example build]] {F4156730} //The UI shows 220 tests as expected.// {F4156731} //The tests appear twice, one for each run. Each test for each run can be accessed directly by clicking the {icon caret-down} next to the test name and select `Show in Build Log`//

Teamcity is relying on the test suite name extracted from the JUnit XML report to display display the suite and its tests. This test suite name is hardcoded, so Teamcity treats all the functional test runs as a single one, preventing from accessing the test details from the web UI. This diff adds an option to `test_runner.py` to allow for setting a name for the test suite, and use it to reflect the intent of the runs. **Teamcity UI before this diff (the `test_runner.py` script is invoked twice on this build)** [[ https://build.bitcoinabc.org/viewLog.html?buildId=25239&buildTypeId=BitcoinABC_BitcoinAbcStaging&tab=buildResultsDiv&guest=1 | Link to the example build]] {F4153505} //The UI show 110 tests instead of 220.// {F4153507} //The tests appear only once, despite they are run twice.// **Teamcity UI after this diff** [[ https://build.bitcoinabc.org/viewLog.html?buildId=259986862&buildTypeId=BitcoinABC_BitcoinAbcStaging&tab=buildResultsDiv&guest=1 | Link to the example build]] {F4153529}6730} //The UI shows 220 tests as expected.// {F4153511}6731} //The tests appear twice, one for each run. Each test for each run can be accessed directly by clicking the {icon caret-down} next to the test name and select `Show in Build Log`//