search

flair / googletest

Automatically exported from code.google.com/p/googletest
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

XML Output Generated for Parameterized tests should contain the parameter values #301

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi, 
I m  currently using gtest release 1.5.0. I have been using type-parameterized 
tests for testing our test cases.
I tried to generate an XML output of it. The XML Output does not print what 
parameters I have sent using parameter.
However whenever I print it on console I get the output.I would require the 
same to be printed in XML Output result for test references.

Please  let me know if this is possible in Gtest upcoming release.

Regards
Prashant Katti

Original issue reported on code.google.com by prashant.katti on 14 Jul 2010 at 8:19

GoogleCodeExporter commented 9 years ago 
(In the future, please use the mailing list 
googletestframework@googlegroups.com for feature requests.)

This requires a change to the XML schema and thus is hard (we need to work with 
tools that consume the format to make sure they don't break).  Google Test 
isn't staffed right now.  Therefore this won't get done unless someone 
volunteers to take the lead.

Original comment by w...@google.com on 22 Jul 2010 at 4:51

GoogleCodeExporter commented 9 years ago

Original comment by w...@google.com on 27 Sep 2010 at 7:26

GoogleCodeExporter commented 9 years ago 
Joey Oravec started to work on this.

I would like to distinguish between value- and type- parameterized
tests.  For the former, I want an attribute like

 value_param=""meeny""

(note the '"' and the lack of "GetParam() = ").

For the latter, I want the attribute to look like:

 type_param="int"

Original comment by w...@google.com on 10 Jan 2011 at 7:15

GoogleCodeExporter commented 9 years ago 
I've uploaded a proposed patch to Rietveld: 
http://codereview.appspot.com/3773042/

Original comment by joeyora...@gmail.com on 27 Jan 2011 at 9:55

GoogleCodeExporter commented 9 years ago 
Fixed in revision 537.

Original comment by vladlosev on 2 Feb 2011 at 3:27