Re: Resource Test Suite

Damn, now to the list.

On 20/02/06, Hugo Palma <[email protected]> wrote:
>
> I spent some time looking at code to see what would be the best way to
> provide such a test suite. I think providing a 100% IDE implementation
> independent test suite would be very very dificult, if not impossible,
> because of all the dependencies to IDE specific code. Still, i think it
> would be "easy" to provide several IDE specific test suites. My idea is
> this:
>
> - Spindle provides the test cases.
> - Each IDE specific implementation provides the fixtures for the tests,
> following the specified rules by the Spindle test cases.
>
> Shortly, the IDE impl. would have to provide to each test the resource
> instance already initialised with the correct state for the test. Spindle
> would define for each test the requirements for the fixtures.
>
> Of course this isn't exactly a compatibility test as the results can be so
> easily forged, but i don't think that's the overall idea anyhow. This would
> definitly help me implementing the IntelliJ plugin as i know for sure, as i
> write my tests, that i'm not covering everything that i should with my
> tests.
>
>
> Cheers
>
> Hugo
>
>
> On 18/02/06, Geoff Longman <[email protected]> wrote:
> > So this evening I added,and committed, tests for the test impls of
> > ICoreResource and IResourceRoot.
> >
> > I'm thinking that this impl will be vital in testing Namespace
> > resolution. In fact I'm starting to see how the Eclipse implementation
> > might extend what is now an almost complete impl of ICoreResource and
> > IResourceRoot.
> >
> > I may move them out of the tests and into the main as an
> > implementation IDE implementers may extend, or not as they see fit. In
> > fact, it may serve more as an example since implementers may see that
> > building a completely custom implementation is better suited/optimized
> > for their platform.
> >
> > That said, I have not moved anything out of test yet.
> >
> > While writing the tests I've noticed that this resource thingy is
> > complicated! Never really dawned on me before as what is now api
> > evolved over a long time a little bit at a time.
> >
> > Would cool if there was a reusable test suite that someone could plug
> > my implementation into and then their implementation into to ensure
> > they both pass the same test. Would mean sharing fixtures. Kinda like
> > a compatibility test suite - does your implementation meet the
> > standard needed by the builder?
> >
> > Have no idea yet how such a thing would be built.
> >
> > Geoff
> >
> > --
> > The Spindle guy.          http://spindle.sf.net
> > Get help with Spindle:
> > http://lists.sourceforge.net/mailman/listinfo/spindle-user
> > Blog:                     http://jroller.com/page/glongman
> > Feature Updates:          http://spindle.sf.net/updates
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642<http://sel.as-us.falkag.net/sel?cmdlnk&kid%103432&bid#0486&dat%121642>
> > _______________________________________________
> > Spindle-developer mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/spindle-developer
> >
>
>