> If you like your testing, it's very good for automating bringing up > stuff, running tests and tearing them down, which you can then do direct > from your JUnit test run.
Yes we plan to do system testing using Smartfrog. You seem to say that I can bring stuff up and tear stuff down from a JUnit test run. I was thinking of embedding Smartfrog in my JUnit tests, although I am not too sure how to do it. My first thought was to look at the ant "deploy" task for guidance on how to control Smartfrog from within java. Is this a sensible approach? Do you have any tips or pointers on how to do this? In the documentation and presentations that I have read about Smartfrog, I've seen tests regarded by Smartfrog as "another thing to deploy". However I have not seen much reference to the idea of tests deploying certain tasks, which would require calling Smartfrog from java test code. This makes me wonder very slightly whether I have some misconception about what Smartfrog should be used for. I think I should give an example of why I am thinking of using Smartfrog in this way. In my case I am looking at a test where I need to kill a process on either one of a pair of machines. Since both machines are simultaneously under control of the tests I cannot simply use a shell command to kill the process because this would mean running the tests on one particular machine, denying me access to the other. Hence my plan was to deploy a "process killer" task on the remote host using Smartfrog from my JUnit code. Thanks, Frank ------------------------------------------------------------------------------ _______________________________________________ Smartfrog-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartfrog-users
