Skip to Content.
Sympa Menu

shibboleth-dev - Re: extension unit testing

Subject: Shibboleth Developers

List archive

Re: extension unit testing


Chronological Thread 
  • From: Tom Scavo <>
  • To:
  • Subject: Re: extension unit testing
  • Date: Fri, 26 Aug 2005 14:47:58 -0400
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lx6JMoNcewKdspbN9d9uwdPYZ6P7FcDTv+GscADPG33hQR4ds3SevOIjJEzL5lQREkbAWaAkjLFTUy3KDruKWH5UlNEToLZNgy2ShK0D1N2c8ti6iDSKAh+IAQy80MkXAaCPNIJRBxWsbc4awC+G0HV5tfBfkfIS3dJn28qluGQ=

On 8/26/05, Walter Hoehn
<>
wrote:
>
> On Aug 26, 2005, at 1:18 PM, Tom Scavo wrote:
>
> > Then what is the recommended approach to post-installation testing?
>
> This doesn't sound like unit testing to me... could you say more
> about what you are hoping to accomplish?

Sure. It basically boils down to this:

1. Pre-GridShib Test Suite:
a) Test Shib AA
b) Test GridShib components

2. Post-GridShib Test Suite:
a) Test GridShib components
b) Test GridShib AA

The idea is to do a pretest of the Shib AA to insure it is fully
functional before GridShib is installed on top. In particular, the
pretest should test client authn as our alpha testing has identified
this as potential source of problems.

Then after the install, the GridShib components are tested again
(assuming the config files are in place) and the AA is tested again
for GridShib functionality. We have (or are developing) tools for 2b,
but we don't know how to do 1a, which is why the work Howard and Will
is doing is interesting.

We currently have tests for 1b and 2a. The latter are simulated
end-to-end tests that workaround limitations in the test framework.
One such workaround led to an earlier request (Bug #424).

Hope this helps,
Tom



Archive powered by MHonArc 2.6.16.

Top of Page