shibboleth-dev - RE: possible testing strategy for Shib 2.0
Subject: Shibboleth Developers
List archive
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: possible testing strategy for Shib 2.0
- Date: Sun, 8 Oct 2006 14:42:37 -0400
- Organization: The Ohio State University
> Note that tomcat isn't required until step 6. Installation of apache
> and the C++ SP is even further down the line. This significantly
> lowers the bar with respect to required technology. Does this seem
> like a reasonable strategy?
Required technology for what? I don't understand the benefit of proving that
running ./ant install results in a useless but "working" system. We already
know that, I think.
OTOH, I agree with extending the current test program to do this because
that's useful in production. This is great stuff for running sites and
testing production changes. That's what I use it for now, that and debugging
attribute issues. But it doesn't seem all that interesting until then.
Your list didn't even mention shibtest until the end, which means all you're
testing is the unmodified defaults.
I'm asusming you're talking about other people testing as opposed to a
testing strategy for the developers. Maybe I'm just confused?
-- Scott
- possible testing strategy for Shib 2.0, Tom Scavo, 10/07/2006
- RE: possible testing strategy for Shib 2.0, Scott Cantor, 10/08/2006
Archive powered by MHonArc 2.6.16.