I would like to be able to test the rendered output from the presentation tier 
in isolation from the business tier.  How can this be accomplished?

Thanks,
Rob

-----Original Message-----
From: Daun DeFrance [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 18, 2006 10:47 AM
To: Tapestry users
Subject: RE: How do you test tapestry 4?

Rob,
We use HtmlUnit against the full war, so the business tier is included.
We use dbunit to stub our database for each test case.  Our business
tier is also unit tested, so we have some "redundant coverage".  We are
tying to approximate, as close as possible, a QA-style of manual testing
of the entire war to help save our human QA for tougher integration
problems.  The strength of this is we can test localization and
edge-conditions, such as form validation, in an automated way and save
the tedious clicking of our QA staff.

Best,
DeFrance

-----Original Message-----
From: Rob Dennett [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 18, 2006 11:42 AM
To: Tapestry users
Subject: RE: How do you test tapestry 4?

Do you use HtmlUnit, etc. on the fully integrated app or do you test the
tapestry side separately from the business tier?

Thanks,
Rob

-----Original Message-----
From: Daun DeFrance [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 18, 2006 10:08 AM
To: Tapestry users
Subject: RE: How do you test tapestry 4?

Rob,
We use HtmlUnit and Canoo Webtest running during a maven 2
integration-test phase.  We use the Jetty6 maven plugin to start a
container and then just fire the tests. It's taken some "creative"
configuration to get it working, but it works well and we are able to
get test reports and cobertura coverage of our classes.

We are now working on building a "Creator-based" framework to get more
granular testing of our pages.  We are doing the opposite process of
you, I guess.  Starting out and working in.

Best,
DeFrance

-----Original Message-----
From: Rob Dennett [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 18, 2006 11:01 AM
To: Tapestry users
Subject: How do you test tapestry 4?

I presume that everyone here separates their business logic from their
pages and that you unit test that code separately.  But how do you test
your pages and components in isolation?  It's all well and good to test
page and component class methods using the Creator, but there doesn't
seem to be anyway to test the rendered output from your pages separate
from the business tier.  You could manually replace the hivemodule with
one that injects fake services, but I would like to keep this process as
automatic as possible.  Could you use something like ant or maven to do
this and maybe to launch a container as well?

 

Thanks for your help,

Rob


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.0/342 - Release Date: 5/17/2006
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.0/342 - Release Date: 5/17/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.0/342 - Release Date: 5/17/2006
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.0/342 - Release Date: 5/17/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.6.0/342 - Release Date: 5/17/2006
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to