[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[hyades-dev] PLEASE READ + RESPOND: Hyades test structure
|
Based on more feedback from last week and on the
committer call I have attached a ZIP file containing my latest proposal for the
Hyades test structure.
The ZIP file should unzip to 3 projects in your
workspace.
Please read the README file in the
"org.eclipse.hyades.tests" project as it contains more detailed information
but here's the gist:
- a single CVS module called
"org.eclipse.hyades.tests" contains all Hyades tests for all
plugins
- every folder inside this CVS module can be
checked out as a Project but the CVS module itself cannot
- one folder (project) called
"org.eclipse.hyades.tests" contains holdall testsuites for all Hyades JUnit and
Hyades Manual tests
e.g.
org.eclipse.hyades.tests/AllJUnitTests.testsuite
org.eclipse.hyades.tests/AllManualTests.testsuite
- there is one folder for each Hyades plugin inside
this CVS module, each of these is called "<normal plugin
name>.tests"
e.g.
HEAD
org.eclipse.hyades.tests (CVS module)
org.eclipse.hyades.tests (contains master
testsuites and possibly results?)
org.eclipse.hyades.statistical.ui.tests
org.eclipse.hyades.perfmon.tests
... (other plugins)
Each plugin test folder is a Java Project and has
the following structure:
a "src" folder for Hyades JUnit
source code
a "bin" folder for the Hyades
JUnit class files
a "junit" folder containing all
Hyades JUnit tests and a Hyades JUnit TestSuite "AllTests" which contains all
the plugin's Hyades JUnit tests
a "manual" folder containing all
Hyades Manual tests and a Hyades Manual TestSuite "AllTests" which contains all
the plugin's Hyades Manual tests
Plugins can define their own structure and nesting within their "junit" and
"manual" folders. All tests to be included in either the overall Hyades
Manual testing or the JUnit testing must be in the "AllTests" testsuite inside
either "junit" or "manual"
The master testsuites inside "org.eclipse.hyades.tests" then reference the
"AllTests" testsuites for each plugin in their behaviour.
This means that:
- a plugin developer can check out individual
plugins' test projects and develop them outwith the entire test bucket.
- if someone wants to run all the Hyades Tests then they
need to check out every folder under the "org.eclipse.hyades.tests" module
as a project and then run the master
testsuites inside the "org.eclipse.hyades.tests" project
- when new tests for a plugin are created they can be
added without modification of the overall "org.eclipse.hyades.tests"
project
- when a plugin first adds tests it must modify the
Hyades overall testsuites (All<blah>Tests) to add its own overall
testsuites (AllTests)
The Hyades Manual testsuites in the example ZIP file are set up and work ok
(try running the overall Hyades AllManualTests testsuite) but I had some
problems running the Hyades JUnit tests. I will try to resolve these but
we can discuss the proposed structure for now.
Perhaps someone more in the know could try running the Hyades JUnit
testsuites just to see that the structure works ok that test type? (there
is only one at the moment - HexData test in org.eclipse.hyades.statistical.ui -
but the hierarchy is there so it should run from the overall testsuites if the
nesting is working ok)
any comments and feedback are very welcome and should go to
hyades-dev
thanks
Antony
|
Attachment:
HyadesTestStructure.zip
Description: Binary data