Chad,
I'm not too familiar with the page flow tests that are in controls. Some of
the existing tests in the coreWeb BVT may already have some of the same test
coverage. If not, then Eddie's suggestion to utilize the existing
TestRecorder framework for any tests you want to move into NetUI, sound good
to me.
I can point you to some of the existing tests...
some control interfaces and implementation files are in
netui/test/webapps/drt/src/org/apache/beehive/netui/test/controls/
and the page flows are in
netui/test/webapps/drt/src/controls/
There are also tests in
netui/test/webapps/drt/{src,web}/pageFlowCore/controlsContextualServices/
netui/test/webapps/drt/{src,web}/pageFlowCore/inheritControls/
netui/test/webapps/drt/{src,web}/pageFlowCore/lifecycle/
Carlin
On 7/6/06, Chad Schoettger <[EMAIL PROTECTED]> wrote:
I've ported most of the core control's drt's from the tch test
framework to Junit tests (using the ControlTestContainer). The only
ones that haven't been ported are those tests which use a page flow as
the control container.
Does anyone have thoughts on what should be done with the tch jpf tests?
I can think of a couple of options:
1 - Go ahead and remove them from the tree, they all have equivalent
JUnit tests with the only difference being the control container. If
removed we would no longer have a dependency on the tch test
framework.
2 - Don't remove them and keep the tch dependency.
- Chad
