I'm planning to design a data collection API for Gallio in an upcoming release that might help here.
However for now what might work best would be for your test to just maintain a tally of the observations and output some statistics to the log to help you understand what happened. One good trick would be to print a "." for each passing sample and an "X" for each failure. Then if you see ".......XXXXX....." you can tell that the failures were clustered. Jeff. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jordan Sent: Wednesday, September 16, 2009 8:27 AM To: MbUnit.User Subject: MbUnit Visualizing errors in collections of data I frequently run test points where I collect the ouput data every 25ms for 5 seconds and test for any anomalies so I am expecting roughly 200 data points where I expect the same result. I use the approximately equal assertion since there are filters applied to the output data. Using the multiple assertions attribute and writing my own assertion method I am able to count the errors and successful results and record it in the test report as only one failure so as not to clutter the report. What I am wondering is if there is a simple way to visualize the errors in the collection. For example I quite often end up with something like Failed 40 out of 200 but without recording all of that data I can not tell if it was the first 40 or the last 40 or intermittently throughout. I was thinking something similar to the navigation stripes in the html test reports only embedded for individual assertions. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
