Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (athena.apache.org: domain of dimi.chr@gmail.com designates
 209.85.221.201 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=IEIu6oNb4RC0W5ROQ7pHZzxzBYVU7so8k9DbNUoZW+pDLYExJM5C3A9tvZP8nFquDA
         KV5K2TM2KEp8TFI4exl4Z+RW4CaBIZdPPCc36W+NFFgocG5W1Y2oxAT4bDxMf471OZmr
         RRSmSorXuAE5dFl66gy3i0CvVbh/0Ht3cWjyw=
MIME-Version: 1.0
In-Reply-To: <Pine.LNX.4.64.0907201746430.10106@haroon.sis.utoronto.ca>
References: <be81a4110907160743h35a296a9w4494c1bdc24b3d80@mail.gmail.com>
	 <8CBD67217B2C7AF-D74-3BF8@webmail-mf15.sysops.aol.com>
	 <5e5424000907190342h48347659vb5d53b716b8aa215@mail.gmail.com>
	 <4A631223.2070900@yahoo.com>
	 <5e5424000907191326q39b9cee5y3eac797f4ec83f5e@mail.gmail.com>
	 <4A639194.1070001@yahoo.com>
	 <be81a4110907191916u17dce601ha353217e6a3b39fa@mail.gmail.com>
	 <Pine.LNX.4.64.0907201013110.27518@haroon.sis.utoronto.ca>
	 <be81a4110907201432g780e050du95f256ceb8d4aa9e@mail.gmail.com>
	 <Pine.LNX.4.64.0907201746430.10106@haroon.sis.utoronto.ca>
Date: Mon, 20 Jul 2009 19:07:09 -0500
Message-ID: <be81a4110907201707x8ad4fd8y4da1b94875fbc332@mail.gmail.com>
Subject: Re: unit testing Struts2 application (with Spring and Hibernate)
From: Dimitrios Christodoulakis <dimi.chr@gmail.com>
To: Struts Users Mailing List <user@struts.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks for clarifying Haroon,

Actually the additions you are mentioning sum up the original testing
code pretty well. Like I said,  from an educational point of view, I
think one can learn a lot about the framework itself by studying that
article and the comments. Thanks for the "preparable" bit too.

As other folks here mentioned, it depends on the testing requirements
of the project when it comes which test strategy to take, or which
tool to use. As a learner, I found it very useful to experiment with
that code.

I haven't tried Selenium yet, but I would be interested to see how it
catches the same errors in the same test cases.

On Mon, Jul 20, 2009 at 5:02 PM, Haroon
Rafique<haroon.rafique@utoronto.ca> wrote:
> On Today at 4:32pm, DC=3D>Dimitrios Christodoulakis <dimi.chr@gmail.com> =
wrote:
>
> DC> Thanks Haroon for the handy advice. That seems to do the trick as far
> DC> as the session object is concerned. The test passes now.
> DC>
>
> Glad it worked out.
>
> DC>
> DC> Would it be easy for someone to extend your code to include actions
> DC> that implement the -aware interfaces? If I wanted to take a shot at
> DC> that, is there a particular point you would suggest I start with?
> DC>
>
> Did you add that code in your Test class? I was actually suggesting that
> you modify the code inside BaseStrutsTestCase. So, I would recommend
> adding a private static HashMap variable called sessionMap in
> BaseStrutsTestCase. And then in the createAction method, issue the
> statement:
> =A0 =A0proxy.getInvocation().getInvocationContext().setSession(sessionMap=
);
>
> Hope that helps.
>
> The only other fringe case that I have dealth with in our code, is when w=
e
> have actions that implement Preparable and are used with a
> ParamsPrepareParams interceptor. I created a method to allow action
> parameters to be set.
>
> /**
> =A0* Sets the action parameters
> =A0* @param parameters Parameters to set
> =A0*/
> protected void setActionParameters(Map<String, String>
> parameters) {
> =A0 proxy.getInvocation().getInvocationContext().
> =A0 =A0 =A0 =A0 =A0 setParameters(parameters);
> }
>
> Then inside my Action Test class, I can issue:
> =A0proxy.setActionParameters(...);
> before:
> =A0proxy.execute();
>
> Cheers,
> --
> Haroon Rafique
> <haroon.rafique@utoronto.ca>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org