[
https://issues.apache.org/jira/browse/PIVOT-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083047#comment-13083047
]
Sandro Martini commented on PIVOT-767:
--------------------------------------
You know that I like very much Grails ... so some idea from it (Grails-2.0
currently in development):
http://blog.springsource.com/2011/06/07/countdown-to-grails-1-4-unit-testing/
For example, are we sure that a base class for all (if any)
xxxTestApplicationContext is enough ?
Probably yes (at least for the initial version) ... but ideas are always useful.
Note that even Griffon ( http://griffon.codehaus.org/ ) , a GUI framework made
in Groovy, and modeled on the same concepts of Grails, has a similar feature.
Of course all those frameworks use the (dynamic) power of Groovy, but maybe
even in "only" plain Java there is something that we can do, or at least try to
support as compatibility.
Some info here: http://groovy.codehaus.org/Testing+Guide
and even here: http://code.google.com/p/spock/
If someone has comments ...
> Better support for Unit Testing of Pivot UI
> -------------------------------------------
>
> Key: PIVOT-767
> URL: https://issues.apache.org/jira/browse/PIVOT-767
> Project: Pivot
> Issue Type: Improvement
> Components: project, wtk
> Environment: n/a
> Reporter: Chris Bartlett
> Assignee: Sandro Martini
> Fix For: 2.1
>
>
> To better support automated Unit Testing of Pivot UI, consider the creation
> of additional concrete ApplicationContext classes like
> UnitTestApplicationContext and/or HeadlessApplicationContext
> See dev mailing list thread here
> http://apache-pivot-developers.417237.n3.nabble.com/Pivot-unit-testing-tp3121005p3121005.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
