[Seaside-dev] JQuery tests and flow

[Julian Fitzell]

On Sun, Nov 15, 2009 at 2:50 PM, Dale Henrichs
<dale.henrichs at gemstone.com> wrote:
>
> ----- "Julian Fitzell" <jfitzell at gmail.com> wrote:
>
> | On Sun, Nov 15, 2009 at 2:30 PM, Randal L. Schwartz
> | <merlyn at stonehenge.com> wrote:
> | >>>>>> "Dale" == Dale Henrichs <dale.henrichs at gemstone.com> writes:
> | >
> | > Dale> I would think that if JQuery itself doesn't depend upon Flow,
> | then the
> | > Dale> tests or at least a subset should be independent of Flow as
> | well.
> | >
> | > I could disagree.  A testing environment might require test
> | harnesses
> | > that are not required for deployment.
> | >
> | > For example, does a running system require SUnit?  No.  You need it
> | only when
> | > you are trying to test something.
> | >
> | > Similarly, tests for jquery could require Flow, where the package
> | itself
> | > for deployment does not.
> |
> | Yes, for example, all of our Functional Tests require the -Component
> | package, even if what they're testing might otherwise not. That said,
> | if we can have all or most of the JQuery functional tests working
> | without Flow (we did the same to the Functional tests by using
> | #show:onAnswer: instead of #call:) that would definitely be A Good
> | Thing.
>
> Is being "A Good Thing" the same as, go ahead and tackle it before beta?:)
>
> I can take a look tomorrow and see if the majority of the tests fall into that category...

If it's relatively easy, sure. :)

Julian