You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Cassie Doll (JIRA)" <ji...@apache.org> on 2008/04/01 17:06:34 UTC

[jira] Updated: (SHINDIG-167) Add jsunit infrastructure and tests to Shindig

     [ https://issues.apache.org/jira/browse/SHINDIG-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cassie Doll updated SHINDIG-167:
--------------------------------

    Attachment: jsunittests.patch

This patch uses the de.berlios version of jsunit because it has an easy to use (mostly) maven plugin. 

The only downside so far is that source js files have to be individually listed (ie *.js doesn't work). I have created two "alltests.js" files which setup the suites and run 2 passing tests. Failing tests also work and stop the maven jetty:run-war from running. 

If there is a more preferred way to set up jsunit integration for apache projects please let me know.
Thanks!

> Add jsunit infrastructure and tests to Shindig
> ----------------------------------------------
>
>                 Key: SHINDIG-167
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-167
>             Project: Shindig
>          Issue Type: Test
>          Components: OpenSocial - Javascript
>            Reporter: Cassie Doll
>            Assignee: Cassie Doll
>         Attachments: jsunittests.patch
>
>
> Shindig needs javascript tests. Patch coming...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.