summaryrefslogtreecommitdiffstats
path: root/src/plugins/platforminputcontexts/compose/compose.json
diff options
context:
space:
mode:
authorTor Arne Vestbø <tor.arne.vestbo@qt.io>2020-01-22 16:43:40 +0100
committerTor Arne Vestbø <tor.arne.vestbo@qt.io>2020-02-03 13:48:25 +0100
commit27db9e458cef512fca3a6b5c9ebbcda7a8172428 (patch)
tree890c771f856b665a9c44ce6111b9f275d4021b3e /src/plugins/platforminputcontexts/compose/compose.json
parent75ad13d2bc414058024bbf8b0886b3d7dd498059 (diff)
testlib: Clarify that our XUnit reporter is actually a JUnit reporter
The reporter was probably named 'xunit' based on the historical use of xUnit to refer to testing frameworks derived from Smalltalk's SUnit. These frameworks typically added their own prefix, e.g. JUnit for Java, RUnit for R, etc. The most popular of these was the JUnit framework, and the corresponding XML output produced by the Ant built tool became somewhat of a de facto standard, which is probably why we chose to model our reporter after it. Nowadays however, naming it 'xunit' is problematic as there is actually a testing famework named xUnit.net, typically shortened to, you guessed it: xunit. Test report consumers will typically have a junit mode, and an xunit mode, and the latter could easily be mistaken for what testlib outputs, unless we clarify this. The clarification also allows us to safely extend our support for the JUnit XML format to incorporate some elements that are nowadays common, but where we are lagging behind the standard. [ChangeLog][QTestLib] The formerly named 'xunitxml' test reporter has been renamed to what it actually is: a JUnit test reporter, and is now triggered by passing -o junitxml to the test binary. Change-Id: Ieb20d3d2b5905c74e55b98174948cc70870c0ef9 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io> Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
Diffstat (limited to 'src/plugins/platforminputcontexts/compose/compose.json')
0 files changed, 0 insertions, 0 deletions