This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 139700 - Move xtest module into misc repository
Summary: Move xtest module into misc repository
Status: RESOLVED FIXED
Alias: None
Product: qa
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Tomas Danek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-11 11:46 UTC by Lukas Hasik
Modified: 2009-07-08 05:36 UTC (History)
5 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Hasik 2008-07-11 11:46:35 UTC
We need to get rid off the old harness xtest after the change to the simpletest infrastructure. It is still worth to
keep the "old" one but it should be moved into http://hg.netbeans.org/main/misc/

Don't forget to remove all the xtest xmls from nbbuild/templates and fix the documentation that may be spread over other
directories
Comment 1 Jesse Glick 2008-07-11 14:35:15 UTC
BTW a good way to see who is "using" it:

hg loc -r tip -0 | xargs -0 fgrep -q xtest

Don't forget to check contrib repo too.

You can move with history if you want:

http://wiki.netbeans.org/HgHowTos#section-HgHowTos-TransferAModuleSHistoryToAnotherRepository
Comment 2 Lukas Hasik 2008-11-19 09:49:02 UTC
it is time to get rid off the xtest -> TM = 7.0 M1
Comment 3 Jesse Glick 2008-11-20 21:28:55 UTC
I just did a quick grep in core-main and contrib to see who is using "xtest", besides main/xtest/** and
main/contrib/xtest{,.examples}/** and main/testtools/** themselves, and .hgignore and .hgmail entries for these subdirs.
The results:

1. */test/{build.xml,build-*.xml,cfg-*.xml} which are residual XTest-based configuration. These files can be deleted at
any time, though some of the less ancient ones may contain useful information about e.g. classpath items which would be
needed after a conversion to NbModuleSuite.

2. Some modules still look for junit.jar or nbjunit.jar or insanelib.jar in xtest/lib.

3. ${xtest.userdata} is used in a few modules. I don't know what this is. Similarly ${xtest.tmpdir}, ${xtest.sketchpad},
${xtest.workdir}, even ${xtest.looks_as_mac} (in core.windows).

5. apisupport.project still provides minimal support for XTest in old platforms, but this should be left alone.

6. editor/test/qa-functional/data/projects/editor_test/src/org/netbeans/test/editor/popup/MainMenuTest/testMainMenu.xml
is probably obsolete.

7. ide.kit/test/qa-functional/data/whitelist_1.txt still refers to XTest runtime classes, which should probably be removed.

8. java.editor/test/qa-functional/src/org/netbeans/test/java/editor/actions/EditorActionsTestCase.java looks up
xtest.home for some reason. NbTestCase uses it somehow too.

9. Some modules customize ${xtest.data}. I think this works in some cases, but it should be deprecated (may not work
from BTD). NbTestCase still uses it.

10. Some modules set ${xtest.jvm.args} to increase max heap, probably unnecessarily.

11. nbbuild/templates/emma.xml has not been fixed up. Anyway there is a separate RFE filed (Tom Wheeler I think) to use
Cobertura.

12. nbbuild/templates/xtest-init.xml needs to go away.
Comment 4 Marian Mirilovic 2009-07-07 14:09:23 UTC
too old -> wontfix
Comment 5 Jesse Glick 2009-07-07 14:31:54 UTC
.
Comment 6 Jesse Glick 2009-07-07 14:35:07 UTC
I already moved sources (preserving history): main #86292bd41454, contrib #12985aeb2a44, misc #e0b6cef29ce5, misc
#1b6eee01e829. The various to-do items I listed have not been done yet, but I can look at them.
Comment 7 Quality Engineering 2009-07-08 05:36:57 UTC
Integrated into 'main-golden', will be available in build *200907080200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/19ac9ff40cf4
User: Jesse Glick <jglick@netbeans.org>
Log: #139700: deleting obsolete XTest build & config files.
Available in history if some information from them is needed to set up dependencies in the new system.