[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] JUnit Framework


David  makes valid points, and is a philosophy we share in the soa components.

1. We need to be careful not to get "tool fever" and end up spending more effort on the tools than what the problem the tools are supposed to solve.
(For example, there's some utilities that load up a workspace with pre-existing projects. This is probably good, but in my experience, most of
us just like to get a copy of some starting version, and then tweak it to suit individual needs. A good general purpose one that met everyone's needs, and
had all kinds options could be developed and maintained ..... but .... not sure it would be worth the effort).


   -We have taken this a step further and declared no inheritance in our testcases. Our main focus is to determine problems in our code not the testcases.

2)  We need to be careful in our test suites, as in our code, to keep our component dependancies minimal and keep them clean. This kind of correct
architecture usually takes more work and planning than just whipping up some quick tools and tweaking copies as needed. But, keep in mind, part
of our componentization effort is not only that someone could "pull" just a subset to use ... that they could "pull" the corresponding test buck to re-run
those tests in what ever context they wanted to. (So .... you wouldn't want to make someone who was using only XML, to have to load J2EE also just to
get some common tool).

- To get around dependencies we created a light weight util (ProjectUnzipUtil). The utility basically unzips projects into the workspace from a zip file location. Typically works in conjunction with a testworkspace. The testworkspace is a simple object that contains zip file path and project/folder/file specific information needed for the testcase.  Teams usually keep a copy of the utility in their test plugins. I have seen mutations of the utility for more complex scenarios, but the original util remains simple and effective. For an example in WTP the util can be found :org.eclipse.wst.common.tests plugin : org.eclipse.etools.common.test.apitools.ProjectUnzipUtil. Used in the org.eclipse.jst.j2ee.flexible.project.apitests.artifactedit plugin:J2EEArtifactEditAPIAllTest... zipped jars found in TestData folder.



Brad Blancett
Rational Tooling
Tie  3-2650
External 919-543-2650



David M Williams/Raleigh/IBM@IBMUS
Sent by: wtp-dev-bounces@xxxxxxxxxxx

12/09/2005 02:21 AM
Please respond to "General discussion of project-wide or architectural issues."

       
        To:        wtp-dev@xxxxxxxxxxx
        cc:        
        Subject:        RE: [wtp-dev] JUnit Framework




I'm sure there could be some good, common, helpful utility classes specifically for WTP, but I'll voice my usual 2 cautions.


1. We need to be careful not to get "tool fever" and end up spending more effort on the tools than what the problem the tools are supposed to solve.
(For example, there's some utilities that load up a workspace with pre-existing projects. This is probably good, but in my experience, most of
us just like to get a copy of some starting version, and then tweak it to suit individual needs. A good general purpose one that met everyone's needs, and
had all kinds options could be developed and maintained ..... but .... not sure it would be worth the effort).


2. We need to be careful in our test suites, as in our code, to keep our component dependancies minimal and keep them clean. This kind of correct
architecture usually takes more work and planning than just whipping up some quick tools and tweaking copies as needed. But, keep in mind, part
of our componentization effort is not only that someone could "pull" just a subset to use ... that they could "pull" the corresponding test buck to re-run
those tests in what ever context they wanted to. (So .... you wouldn't want to make someone who was using only XML, to have to load J2EE also just to
get some common tool).


So, speaking of wasting time ... that response was a lot longer than it needed to be. :)  

Do feel free to propose any process or tool improvements you can
contribute!


Thanks,


David





"Gerry Kessler" <gerry.kessler@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

12/08/2005 04:01 PM

Please respond to
"gerry.kessler@xxxxxxxxxx" and "General discussion of project-wide or architectural issues."

To
"Jeffrey Liu" <jeffliu@xxxxxxxxxx>, "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject
RE: [wtp-dev] JUnit Framework







Thanks Jeffrey.   I will take a look.

 

We have started creating test cases for the jsf tooling code we have so far.   You never know.   Maybe we will come up with something that can be useful to all.

-----Original Message-----
From:
Jeffrey Liu [mailto:jeffliu@xxxxxxxxxx]
Sent:
Thursday, December 08, 2005 12:48 PM
To:
gerry.kessler@xxxxxxxxxx; General discussion of project-wide or architectural issues.
Subject:
RE: [wtp-dev] JUnit Framework



Gerry,


There are some abstract performance testcases in org.eclipse.wst.common.tests.performance that you may find useful, depending on what you want to do... Other than that, I'm not aware of any. Will you be interested in contributing some :)?


Thanks,


Jeffrey Liu
IBM Rational Software - Performance Analyst
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/R8V/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
jeffliu@xxxxxxxxxx


"Gerry Kessler" <gerry.kessler@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

12/08/2005 03:34 PM

Please respond to
"gerry.kessler@xxxxxxxxxx" and "General discussion of project-wide or architectural issues."


To
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject
RE: [wtp-dev] JUnit Framework









Thanks David.   Yes, I saw that and I know I must use this to eventually hook into the build-and-run-tests process.


What I really meant to say, I guess, is there a set of WTP specific TestCase/TestSuite sub-classes that are commonly used?  Is there a set of common utility classes used to do common setup-type things?  


Thanks,

GK

-----Original Message-----
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]On Behalf Of David M Williams
Sent:
Thursday, December 08, 2005 12:29 PM
To:
wtp-dev@xxxxxxxxxxx
Subject:
Re: [wtp-dev] JUnit Framework



Yes, sort of .... we use the same as "base Eclipse" .. its available from their download page.

Its a zip that starts with "
eclipse-test-framework- "

You can see any of our test plugins, which have a test.xml file that "hooks in" to it.

David


"Gerry Kessler" <gerry.kessler@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

12/08/2005 03:01 PM

Please respond to
"gerry.kessler@xxxxxxxxxx" and "General discussion of project-wide or architectural issues."


To
"wtp-dev@xxxxxxxxxxx" <wtp-dev@xxxxxxxxxxx>
cc
Subject
[wtp-dev] JUnit Framework











Hi All,


Has there been a common testing framework developed for WTP that one might be able to use?   I don't see one, but I could have missed it.   If not, is one being considered?


Thanks,

Gerry Kessler

WTP JSF Tools Team
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev

_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev