Is it possible to add an option (either as a flag or in testng.xml) that will direct TestNG to strip out the TestNG related stuff from the stacktrace? Our reports are getting a little too crowded and for people who don't care much about TestNG internals, it's just a redundant info.
> Is it possible to add an option (either as a flag or in testng.xml) that > will direct TestNG to strip out the TestNG related stuff from the > stacktrace? > Our reports are getting a little too crowded and for people who don't care > much about TestNG internals, it's just a redundant info.
> Eran if you are using the Eclipse plugin I think this is already > supported by default.
> ./alex > -- > .w( the_mindstorm )p.
> On 6/19/06, Eran <eran...@gmail.com> wrote: > > Hi,
> > Is it possible to add an option (either as a flag or in testng.xml) that > > will direct TestNG to strip out the TestNG related stuff from the > > stacktrace? > > Our reports are getting a little too crowded and for people who don't > care > > much about TestNG internals, it's just a redundant info.
> I'm using IntelliJ but I was actually referring the html reports (we usually > invoke TestNG with Ant).
> Regards, > Eran
> On 6/19/06, Alexandru Popescu > <the.mindstorm.mailingl...@gmail.com> wrote:
> > Eran if you are using the Eclipse plugin I think this is already > > supported by default.
> > ./alex > > -- > > .w( the_mindstorm )p.
> > On 6/19/06, Eran <eran...@gmail.com > wrote: > > > Hi,
> > > Is it possible to add an option (either as a flag or in testng.xml) that > > > will direct TestNG to strip out the TestNG related stuff from the > > > stacktrace? > > > Our reports are getting a little too crowded and for people who don't > care > > > much about TestNG internals, it's just a redundant info.
> I think this is doable too, so I will wait for other opinions before > cutting out the TestNG related stack frames.
> ./alex > -- > .w( the_mindstorm )p.
> On 6/19/06, Eran <eran...@gmail.com> wrote: > > Hi Alexandru,
> > I'm using IntelliJ but I was actually referring the html reports (we > usually > > invoke TestNG with Ant).
> > Regards, > > Eran
> > On 6/19/06, Alexandru Popescu > > <the.mindstorm.mailingl...@gmail.com> wrote:
> > > Eran if you are using the Eclipse plugin I think this is already > > > supported by default.
> > > ./alex > > > -- > > > .w( the_mindstorm )p.
> > > On 6/19/06, Eran <eran...@gmail.com > wrote: > > > > Hi,
> > > > Is it possible to add an option (either as a flag or in testng.xml) > that > > > > will direct TestNG to strip out the TestNG related stuff from the > > > > stacktrace? > > > > Our reports are getting a little too crowded and for people who > don't > > care > > > > much about TestNG internals, it's just a redundant info.
> Is it possible to add an option (either as a flag or in testng.xml) > that will direct TestNG to strip out the TestNG related stuff from > the stacktrace? > Our reports are getting a little too crowded and for people who > don't care much about TestNG internals, it's just a redundant info.
> Good idea though to extend it to the core reports!
> On Jun 19, 2006, at 4:05 PM, Eran wrote:
> > Hi,
> > Is it possible to add an option (either as a flag or in testng.xml) > > that will direct TestNG to strip out the TestNG related stuff from > > the stacktrace? > > Our reports are getting a little too crowded and for people who > > don't care much about TestNG internals, it's just a redundant info.
Yeah good idea to cut it out from the source, with a flag to enable it (which you'd only want to do if you're one of the handful of people who care about tng internals!)
On Jun 19, 2006, at 6:06 PM, Alexandru Popescu wrote:
> What I am wondering is if we shouldn't just cut it out (instead of > using another parameter for doing it). What's your call?
> ./alex > -- > .w( the_mindstorm )p.
> On 6/19/06, Hani Suleiman <h...@formicary.net> wrote:
>> The IDEA plugin already does that ;)
>> Good idea though to extend it to the core reports!
>> On Jun 19, 2006, at 4:05 PM, Eran wrote:
>>> Hi,
>>> Is it possible to add an option (either as a flag or in testng.xml) >>> that will direct TestNG to strip out the TestNG related stuff from >>> the stacktrace? >>> Our reports are getting a little too crowded and for people who >>> don't care much about TestNG internals, it's just a redundant info.
> Yeah good idea to cut it out from the source, with a flag to enable > it (which you'd only want to do if you're one of the handful of > people who care about tng internals!)
> On Jun 19, 2006, at 6:06 PM, Alexandru Popescu wrote:
> > What I am wondering is if we shouldn't just cut it out (instead of > > using another parameter for doing it). What's your call?
> > ./alex > > -- > > .w( the_mindstorm )p.
> > On 6/19/06, Hani Suleiman <h...@formicary.net> wrote:
> >> The IDEA plugin already does that ;)
> >> Good idea though to extend it to the core reports!
> >> On Jun 19, 2006, at 4:05 PM, Eran wrote:
> >>> Hi,
> >>> Is it possible to add an option (either as a flag or in testng.xml) > >>> that will direct TestNG to strip out the TestNG related stuff from > >>> the stacktrace? > >>> Our reports are getting a little too crowded and for people who > >>> don't care much about TestNG internals, it's just a redundant info.
|
