I am pretty sure this is a very common scenario and there must be a solution for this.
We have multiple web application, one of them single sign on and others are individual app for different departments. To test any of the department application, we need to first authenticate using single sign-on and then move on do the respective work. The question is how to achieve this. One way I can think of is to actually call the authenticate URL by direct HTTPS request from my test method (apache common software or built in java library) and then use the returned cookie, set it in the session, invoke action classes to test particular functionality Otherwise the problem is that the test class I write will not find single sign on action class since test classes are deployed along with the department applications only. Any better idea on how to achieve this -- Thanks Sushil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]