[
https://issues.apache.org/jira/browse/PIVOT-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057325#comment-13057325
]
Sandro Martini commented on PIVOT-767:
--------------------------------------
Hi Chris,
I'm happy you have this idea too ... it's something I had some toughs some time
ago, and that in my opinion should be improved to have more test coverage,
reducing manual testing of applications ...
We have to see if some classes related to user interaction (mouse, keyboard,
etc) have to be written/rewritten (or extend existing, if possible) for this to
work.
Maybe we could even write some Pivot-related class that extends JUnit to
simplify things (if needed).
Then we have to see where is the good place to put all this stuff, could be a
new sub-project in pivot workspace like test (but attention to avoid confusion
with tests subproject) or tools (for developers-only pivot tools).
Note: for the 2.1 release probably we can move the JUnit required version to
4.8.2 (released during 2010), as seen here:
https://github.com/KentBeck/junit/downloads
Only note that inside eclipse usually embedded junit is older ...
Bye
> Consider the creation of additional concrete ApplicationContext classes to
> better support unit testing of Pivot UIs
> -------------------------------------------------------------------------------------------------------------------
>
> Key: PIVOT-767
> URL: https://issues.apache.org/jira/browse/PIVOT-767
> Project: Pivot
> Issue Type: Wish
> Components: project, wtk
> Environment: n/a
> Reporter: Chris Bartlett
> Priority: Minor
> Fix For: 2.1
>
>
> 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
