Why a verbose level in Tests and Suites ?

[Claude Quezel]

Why would a suite or a test want to specify a verbose level except for tracing or debugging? Why would we want separate verbose levels for tests in the same suite? Why would we want to pollute TestNG suite with verbose statements for debugging or tracing reasons when this can be done on the command line using the –log option? i.e. are the verbose attributes useful?

Claude
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=31480&messageID=61004#61004

[Cédric Beust ♔]

They're just here for symmetry.  Typically, attributes defined on <suite> can also be defined on <test> (and if they are present on both, the ones on <test> will take precedence).

It's a simple rule and I didn't see any reason not to apply it to verbose as well.

I don't really find it useful myself but I know better than assuming what users will want to do...

--
Cedric

--
Cédric

[Claude Quezel]

Actually I was refereing to both Suite and Test verbose attribute. I think the intent of these attributes is strictly debugging/tracing. I would suggest to remove these from the TestNG Suite.xml definition and have an alternate method of debugging (tracing) suites and tests. This way I could enable/disable logging/verbose without altering TestNG Suite.XML files. The end result would be the same (I'm just pushing towards a logging API).

Claude
---------------------------------------------------------------------
Posted via Jive Forums

http://forums.opensymphony.com/thread.jspa?threadID=31480&messageID=62030#62030

[Cédric Beust ♔]

Hi Claude,

Note that you can specify the log level on the command line or from your ant task.  Not as flexible as what you have in mind, though...

--
Cedric

--
Cédric