pivot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roger Whitcomb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIVOT-1029) Need some tests of things in the various "wtk" Component classes
Date Thu, 15 Feb 2018 23:42:00 GMT

    [ https://issues.apache.org/jira/browse/PIVOT-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366425#comment-16366425

Roger Whitcomb commented on PIVOT-1029:

First "test" of this idea:
* Needed to update the classpath in the "test" macro to include all the built .jar files so
that the Theme can be loaded (by the Service provider(s) in the .jar file).
* Fix some of the stuff in Meter and its skin.
* Then add the MeterTest class to actually test the listeners being fired at the proper time.

Sending build.xml
Sending wtk\src\org\apache\pivot\wtk\Meter.java
Adding wtk\test\org\apache\pivot\wtk\test\MeterTest.java
Sending wtk-terra\src\org\apache\pivot\wtk\skin\terra\TerraMeterSkin.java
Transmitting file data ....done
Committing transaction...
Committed revision 1824382.

> Need some tests of things in the various "wtk" Component classes
> ----------------------------------------------------------------
>                 Key: PIVOT-1029
>                 URL: https://issues.apache.org/jira/browse/PIVOT-1029
>             Project: Pivot
>          Issue Type: Test
>          Components: tests, wtk
>            Reporter: Roger Whitcomb
>            Assignee: Roger Whitcomb
>            Priority: Minor
> I noticed some things that were not quite right (listener being fired always instead
of on a change) in a Component, and it occurred to me that things like this need to be tested
systematically.  One way to do that would be to introduce component-based tests in the "wtk/test"

This message was sent by Atlassian JIRA

View raw message