You could use Fastnet to add reliability on resources. I'm not sure how long they're retained if they're unavailable though.
On Feb 12, 2008 2:32 PM, Kevin Brown <[EMAIL PROTECTED]> wrote: > On Feb 12, 2008 8:54 AM, Cassie <[EMAIL PROTECTED]> wrote: > > > The compliance tests will be hosted on the spec website. I do not feel > > that > > we will need to bring in snapshots into the shindig project because it > ill > > most likely just be a gadget that your container needs to run. > > > We might need snapshots for automated testing -- it's difficult to do > automated builds that depend on http resources. In any case it would be an > exact copy. I'd prefer to avoid this but unfortunately the internet isn't > that reliable :). > > > > > > However, the sample container and the soon to be written server backed > > opensocial container definitely need tests in shindig because they are > > very > > buggy! So it would be great to get some real tests for data into it. > > > > - Cassie > > > > > > On Tue, Feb 12, 2008 at 4:35 AM, Kevin Brown <[EMAIL PROTECTED]> wrote: > > > > > On Feb 12, 2008 3:51 AM, Reinoud Elhorst <[EMAIL PROTECTED]> wrote: > > > > > > > Thanks Paul, > > > > > > > > I was about to suggest creating something like this! We'll be sure > to > > > use > > > > this (and/or any other testsuite), and contribute any tests that we > > feel > > > > are > > > > not covered once we feel we have the implementation right! > > > > > > > > I'm wondering whether this should be part of Shindig, and I think > so. > > A > > > > reference implementation is most useful when accompanied by a lot of > > > tests > > > > that confirm any other implementation is "correct". > > > > > > > > > It's best that conformance tests be kept next to the specs, and > > shindig's > > > individual unit tests focused on shindig implementation details. I > don't > > > think it makes sense to have to check out shindig just so that you can > > run > > > conformance tests. > > > > > > We might want to grab snapshots and pull them into shindig so that > they > > > can > > > be used for automated testing, but the "ownership" of any conformance > > test > > > belongs in the spec. The test should change when the spec changes, not > > > when > > > shindig changes. > > > > > > Or would these tests be mainly focussed on implementing containers > > > (assuming > > > > an already correct gadget server)? > > > > (Since a sample container is part of > > > > Shindig as well, I still think the tests should be in there as > > well...) > > > > > > > > Reinoud > > > > > > > > On 2/12/08, Paul Lindner <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi, > > > > > > > > > > I've been compiling an OpenSocial Unit Test application for some > > time > > > > > now. If you have small snippets of test code please consider > > > > > submitting them to me and I'll merge it into the test suite. > > > > > > > > > > You can find the current version of the Unit Test Application > here: > > > > > > > > > > http://www.inuus.com/os/unittest-os.xml > > > > > > > > > > This will help hi5 and other containers conform to the > > specification. > > > > > > > > > > -- > > > > > Paul Lindner > > > > > hi5 Architect > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > ~Kevin > > > > > > If you received this email by mistake, please delete it, cancel your > > mail > > > account, destroy your hard drive, silence any witnesses, and burn down > > the > > > building that you're in. > > > > > > > > > -- > ~Kevin > > If you received this email by mistake, please delete it, cancel your mail > account, destroy your hard drive, silence any witnesses, and burn down the > building that you're in. >
