Hmm. The trick is that this mechanism is quite general and applies to more than just CSV files. So identifying cases by row number by default is right out. It would make it too difficult to figure out what's going on with things like RowTests that have unusual ordering properties (dependent upon .Net reflection).
In Alpha 3, there have been a number of enhancements to the report that might help you out here: 1. Leaf nodes automatically start out collapsed if JavaScript is enabled. This helps to reduce some of the noise when reading the report since the test step names will line up. It ends up looking kind of like a table. 2. There is a report navigation tab on the side that should help you quickly find failing tests. 3. If you want to, it is possible to create a test decorator that changes the name of the test. So if you wanted to, you could maybe sneak a Row # in the name... Anyways, if you have a little time, I'd love it if you could send me a quick mockup of your ideas for improving the layout. I'm having a little difficulty imagining how a tabular layout would work, particularly with a very large number of columns. Jeff. -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Jordan Sent: Wednesday, April 16, 2008 1:23 PM To: MbUnit.User Subject: MbUnit Re: V3 DataTest I have been trying out the CSVData attribute with MbUnit3. One thing I like better over this than the v2 addin is that the Test Explorer doesn't make a seperate entry for every row in the CSV file. However, in the report details it is listing the test name with all of the inputs for each row of the CSV file. In my tests I have a lot of columns in the csv file, this results in a very confusing report since it isn't obvious in the report what each value is. If it's possible I would either like to see these inputs with the header row in a table so that they are easily identified or else it would be simpler to just list the test name and row number from the CSV file. What do you think? Thanks, Jordan On Apr 7, 11:39 am, "Jeff Brown" <[EMAIL PROTECTED]> wrote: > Yes. > [CsvData] will be in the next release. I was planning to ship last > night but I ended up doing other stuff. Should be within the next couple of days. > > If you're eager to try it out, go grab a recent nightly > fromhttp://ccnet.gallio.org/Distributables > > Jeff. > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > On > > Behalf Of Jordan > Sent: Monday, April 07, 2008 9:18 AM > To: MbUnit.User > Subject: MbUnit V3 DataTest > > I have been using the QE.Framework mentioned in this > post:http://blog.bits-in-motion.com/2007/09/release-early-release-ofte > n.html > > Jeff mentioned that he was working on perfecting the feature in MbUnit > Gallio and I was wondering if it had made it into MbUnit V3 yet? I am > using the CsvResource attribute of the QE.Framework. > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
