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 18880 - All configurations are compiled
Summary: All configurations are compiled
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: xtest (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-20 16:46 UTC by Jan Zajicek
Modified: 2003-07-02 12:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Zajicek 2001-12-20 16:46:58 UTC
Situation: I want to run my qa-functional openide tests. Why are all untit and
regression tests compiled too? This may lead into test execution failure in case
i.e. another configuration needs special classpath to compile, which is set
according to the xtest.testtype property. I modified the build.xml in openide to
 set testtype property as follows to worarouded this issue:

<property name="compile.srcdir" value="${xtest.testtype}/src"/>

Please move this property into the harness xml, because it isn't used anywhere
in the build.xml. And think about the compilation scheme, so there isn't
compiled anything more than is needed while test execution.
Comment 1 Martin Brehovsky 2001-12-20 17:15:30 UTC
We should probably add a new property to TestBag configuration in cfg
files, similar to executor.  This property could be called "compiler"
and would allow each TestBag use its own target to compile tests. This
target could set appropriate classpath, use custom compilers (e.g.
rmic), etc ...

We could also introduce a feature, which would allow to use test type
specific build.xml. So when test type will not have its own build.xml
it will use by detault the original one. If it will have its own
build.xml then this script should be used instead.

Both this feature would solve many headaches when several testwriters
and developers have to use only one build.xml for one module.
Comment 2 L Martinek 2002-01-25 10:23:11 UTC
Compilers were introduced into xtest harness. To use compilers do
following:

1. Define compilers in cfg-xxx.xml. If compiler has attribute
default="true" then this compiler is used for all testbags inside this
cfg file. Otherwise you has to add attribute compiler to every
testbag. Implementation of compilers can be in separate script.

2. Change target buildtests in build.xml. Originally target buildtests
in module_harness.xml was called. Change this taget to only call
target compiler-launcher in module_harness.xml.

    <target name="buildtests">
       <ant dir="." antfile="${xtest.module_harness.antfile}"
             target="compiler-launcher"/>
    </target>

Move any compiling stuff to compilers.

3. Implement compilers. All compilers defined in cfg file has to be
implemented. Just e.g. create new target unit-compiler.

Look at http://xtest.netbeans.org/XTest_module_template.html for
description of build.xml. Also look at xtest/examples/MyModule/test 

Note: If you start to use compilers all testtypes has to use them.
It's because target buildtests in build.xml is changed to call
compiler-launcher so then all tests will require compilers
Comment 3 Jan Zajicek 2002-02-05 10:37:35 UTC
Works ok.
Comment 4 Quality Engineering 2003-07-02 12:21:59 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.