launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #07704
Re: Importing JavaScript test modules (no need to set up the Runner)
-
To:
launchpad-dev@xxxxxxxxxxxxxxxxxxx
-
From:
"Francis J. Lacoste" <francis.lacoste@xxxxxxxxxxxxx>
-
Date:
Tue, 02 Aug 2011 09:58:19 -0400
-
In-reply-to:
<CALL7ch=R5xRKJwvo1e8G7fy-HK25rhLkV9fPjP+kCBWPK8QjUw@mail.gmail.com>
-
Organization:
Canonical
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
On 11-08-01 05:56 AM, Gavin Panella wrote:
> If you're writing a JavaScript test module, you'll be familiar with
> putting this at the end of your YUI().use(...) block:
>
> Y.lp.testing.Runner.run(suite);
>
> That's neat and concise but it causes a problem: there's no way to
> just import the test module.
>
> I've been trying out an alternative approach (test *modules* that
> don't care about the runner). It's already in the tree so you could
> use it too. If no one objects I'll convert existing tests later in the
> week or next, so read the following page if this interests you:
>
> https://dev.launchpad.net/GavinPanella/ImportingJavaScriptTestModules
>
I was wondering why we want to do this, but the wiki page does an
excellent job to answer my question!
Thanks for that!
But does this mean that writing the tests in a module will be bundled in
the launchpad.js file? Are we shipping useless test code to our users?
--
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References