You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Chad Schoettger (JIRA)" <de...@beehive.apache.org> on 2006/06/27 21:19:29 UTC
[jira] Created: (BEEHIVE-1129) Port existing TCH Beehive controls
tests to JUnit
Port existing TCH Beehive controls tests to JUnit
-------------------------------------------------
Key: BEEHIVE-1129
URL: http://issues.apache.org/jira/browse/BEEHIVE-1129
Project: Beehive
Type: Improvement
Components: Controls
Reporter: Chad Schoettger
The TCH controls test framework makes it difficult to create new tests and debug existing controls tests. Now that we have the ControlTestContainer available all of the controls tests currently under TCH should be ported to JUnit. This will dramatically simplify unit test creation for controls and also be more easily maintained.
All new controls tests should be added as JUnit tests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-1129) Port existing TCH Beehive controls
tests to JUnit
Posted by "Chad Schoettger (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-1129?page=all ]
Chad Schoettger resolved BEEHIVE-1129.
--------------------------------------
Fix Version/s: v.next
Resolution: Fixed
Assignee: matt c (was: Chad Schoettger)
All controls drt's have been ported to Junit. The set of controls drts which depended on jpf's has been moved to the netui test suite controlsWeb web app.
> Port existing TCH Beehive controls tests to JUnit
> -------------------------------------------------
>
> Key: BEEHIVE-1129
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1129
> Project: Beehive
> Issue Type: Improvement
> Components: Controls
> Reporter: Chad Schoettger
> Assigned To: matt c
> Fix For: v.next
>
>
> The TCH controls test framework makes it difficult to create new tests and debug existing controls tests. Now that we have the ControlTestContainer available all of the controls tests currently under TCH should be ported to JUnit. This will dramatically simplify unit test creation for controls and also be more easily maintained.
> All new controls tests should be added as JUnit tests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-1129) Port existing TCH Beehive controls
tests to JUnit
Posted by "Chad Schoettger (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-1129?page=all ]
Chad Schoettger reassigned BEEHIVE-1129:
----------------------------------------
Assignee: Chad Schoettger
> Port existing TCH Beehive controls tests to JUnit
> -------------------------------------------------
>
> Key: BEEHIVE-1129
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1129
> Project: Beehive
> Issue Type: Improvement
> Components: Controls
> Reporter: Chad Schoettger
> Assigned To: Chad Schoettger
>
> The TCH controls test framework makes it difficult to create new tests and debug existing controls tests. Now that we have the ControlTestContainer available all of the controls tests currently under TCH should be ported to JUnit. This will dramatically simplify unit test creation for controls and also be more easily maintained.
> All new controls tests should be added as JUnit tests.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira