diagram of tests dependencies

Cedric, All,

I was thinking about adding a new feature to TestNG. What I would like
to have is a dot (graphviz) diagram of test dependencies. ...not sure
if that is of any use at all, but I feel like it might be fun. :)

I don't know TestNG codebase very well (if at all), so I would like to
ask you for hints on how to proceed.

I guess, that after I feed TestNG with tests, e.g. like this:
TestNG testng = new TestNG();
testng.setTestClasses/Suites(...)
then TestNG holds some internal structure which describes dependencies of tests.

Now the question is: "how can I access it?"

What I figured out is that it is possible by implementing IReporter
interface. This seems to be pretty easy, but there is another issue to
solve. Reporters come into action after tests are finished. I would be
more happy to be able to generate it without running any tests. How
can I skip all tests ? Should I write an annotation transformer that
would make all tests "enabled=false"?

--
Cheers,
Tomek Kaczanowski

Hi Tomek,

Hi Cedric,

...that is really annoying! ;)

I will have a look at this. Thank you !

--
Regards / Pozdrawiam
Tomek Kaczanowski

Hi Cedric,

I tried to use it but with limited success. I run ant build of testng
and got a lot of dot files in /tmp/TestNG-whatever folder. They are
not exactly what I would like to have. It seems like no real test
methods names are used, but some fancy f1, f2 labels.

What I would like is to have clusters of groups and dependencies of
groups and methods. For example something like this:

digraph G {

subgraph cluster_0 {
style=filled;
color=lightgrey;
node [style=filled,color=white];
testA;
testB;
testC;
label = "smoke tests";
}

subgraph cluster_1 {
node [style=filled];
testD;
testE -> testF;
label = "real fun tests";
color=blue
}
testD -> testB;

}

which generates the following diagram: http://tinyurl.com/5s6bmss

(this is just an example of the general idea, would need to work more
on this so the stuff is readable in case of thousands of tests etc.0

Would it be possible with GraphThreadPoolExecutor or should I try to
implement it using the IReporter approach described earlier?

--
Cheers,
Tomek Kaczanowski

Tomek,

Hi Cedric,

So one option is to fork/hack TestNG and change
GraphThreadPoolExecutor to whatever suits me. Ok, good to know, thanks
for this tip.

But that is not really user-friendly, is it? I mean, it would be much
easier to have it pluggable, which means without changing TestNG. That
is why I ask you so stubbornly about implementing IReporter :)

> --

Tomek,

Cedric, All,

> Keep us posted!
you can follow the development on GitHub
https://github.com/tomekkaczanowski/testng-test-dependencies-reporter
> > >> testng-dev+...@googlegroups.com<testng-dev%2Bunsu...@googlegroups.com>
> > .
> > > testng-dev+...@googlegroups.com<testng-dev%2Bunsu...@googlegroups.com>
> > .
> > testng-dev+...@googlegroups.com<testng-dev%2Bunsu...@googlegroups.com>
> > .

Cedric, All,

I hacked a first version and described it on my blog http://is.gd/mFIh3J

The code is on github http://is.gd/Lzjs41

Hopefully someone will find it useful. :)

--
Cheers,
Tomek Kaczanowski

On 23 Sty, 16:58, Tomek Kaczanowski <kaczanowski.to...@gmail.com>
wrote:
> you can follow the development on GitHubhttps://github.com/tomekkaczanowski/testng-test-dependencies-reporter
> > > >> testng-dev+...@googlegroups.com<testng-dev%2Bunsubscribe@googlegrou­ps.com>
> > > > testng-dev+...@googlegroups.com<testng-dev%2Bunsubscribe@googlegrou­ps.com>
> > > testng-dev+...@googlegroups.com<testng-dev%2Bunsubscribe@googlegrou­ps.com>

Hi Tomek,

FYI, I added a link to your blog post from the documentation:

done

Yes, if I am only interested in seeing the dependencies then running
tests is a waste of time.
What do you mean "with simple introspection"? You mean I should use
standard Java mechanism, or is there something in the API of TestNG
that might help me to discover test dependencies without running the
tests?

Thanks for making me famous! ;)

--
Cédric

Hi Cedric,

one more question (and probably not the last one).

If a configuration method (e.g. @BeforeClass) fails, then tests, that
should be run after it, are skipped, right?

Now, I would like to learn about why a particular test was skipped.
That is, I want to know because of which failed set up method it was
skipped.

Is it possible? AFAIK configuration methods are not listed by
getMethodsDependedUpon method of ITestNGMethod.

2011/2/15 Cédric Beust ♔ <ced...@beust.com>:

Hi Tomek,

--
Cédric