The problem with this design is that when test2 fails, stopTest is
skipped. I thought that with alwaysRun=true this method would always
get called. How can I assure that it is always called?
I have another test class, where I have about 8 tests that are
independent of each other, and thus I made all of them dependent only
on setUp(). However, I am not certain how I can tie in the stopTest()
method. It does not depend on any other method in particular but
needs to be executed once all the test methods complete. What's the
correct approach here?
You should not be mixing @Test with @AfterSuite, you should break down this
code in two categories (which one is really a test and which one is used to
tear down your test) and put these in separate methods.
Can you do this and post your updated code if you're still having problems?
> The problem with this design is that when test2 fails, stopTest is
> skipped. I thought that with alwaysRun=true this method would always
> get called. How can I assure that it is always called?
> I have another test class, where I have about 8 tests that are
> independent of each other, and thus I made all of them dependent only
> on setUp(). However, I am not certain how I can tie in the stopTest()
> method. It does not depend on any other method in particular but
> needs to be executed once all the test methods complete. What's the
> correct approach here?
> You should not be mixing @Test with @AfterSuite, you should break down this
> code in two categories (which one is really a test and which one is used to
> tear down your test) and put these in separate methods.
> Can you do this and post your updated code if you're still having problems?
> --
> Cedric
> On Fri, Nov 6, 2009 at 6:35 PM, Lidia <lid...@gmail.com> wrote:
> > Hello
> > I have some basic questions related to method dependency. I have the
> > following test:
> > @Test (groups = {"jsf", "ajax", "crossbrowser"})
> > public class TestCrossbrowserUpdateAttr extends SeleneseTestCase {
> > (...)
> > The problem with this design is that when test2 fails, stopTest is
> > skipped. I thought that with alwaysRun=true this method would always
> > get called. How can I assure that it is always called?
> > I have another test class, where I have about 8 tests that are
> > independent of each other, and thus I made all of them dependent only
> > on setUp(). However, I am not certain how I can tie in the stopTest()
> > method. It does not depend on any other method in particular but
> > needs to be executed once all the test methods complete. What's the
> > correct approach here?