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.
During the discussion after addition of schema2beans module to regular NetBeans build it has been agreed on that the set of tests will be changed to be exacuted daily by the xtest framework. This issues is created to ensure that this will really be done before release of 3.4. That is why it is a defect and p1.
So any progress on this or what?
This bug is reported in version <= 3.4dev and still not fixed. Due to that it forbids the release candidate for 3.4 to be promoted. Are you aware of that and are you intensively working on the fix? If not, you should consider some corrective action.
Cliff sent an e-mail '[nbdev] how do I put my tests into the daily xtest runs?'. Sorry but search engine on website doesn't show link to this. I am not sure about the conclusion.
Reassign the bug to xtest maintainer? Maybe Martin Brehovsky? Martin Balin knows for sure.
This issue depends on issue 25046, which is xtest task to add tests to daily execution. Unfortunately tests for schema2beans are not ready to put to daily execution and its buildscript has to be changed (see above issue). When it is done tests will be put to daily execution.
I could go through the effort and figure out what is holding up issue 25046 (I've been able to run the tests on 2 separate machines by just running `ant test`). But is it worth it for 3.4? I don't think I should change any source code at this point, and changing the big build and/or test scripts might not be the best idea.
"But is it worth it for 3.4?" The only reason I keep talking about the issue is that schema2beans was added to the build without following the rules for adding new modules and we agreed that having tests integrated is a necessary thing to leave it in 3.4. Actually, I do not care whether tests will run in 3.4 or only in dev, I just came to conclusion, that next time, it is not possible to rely on promises. Thus I will stick on fulfilling all "addition to dev trunk" criteria before new module appears there. But that is a different story that does not touch schema2beans.
Hi, these issues block the 3.4 release. It has been suggested on nbdev that those that are not going to be fixed for 3.4 FCS (waivers) change the target milestone to "future" or "4.0". I'd like to suggest you to do so, if you and your reporter agree on that.
I've changed the target milestone to "future". I'll work out whatever issue there is with the main tests and my tests in the trunk.
We're close to the 3.5 code-freeze and there doesn't seem to be much progress on this one. Doesn't sound like a P1 DEFECT to me. I don't believe users are directly affected by this issue. Downgrading to P3, although more appropriate might be to track this issue as a P1 TASK.
Changing the priority is fine with me. This issue depends on 25046 right now, and I'm making slow progress on that.
There are 26 tests running in daily builds now: http://www.netbeans.org/download/xtest-results/netbeans_dev/200308200100/development-unit/linux-2.4.18-19.8.0-i386/testrun_030820-092630/testbag_11/htmlresults/testbag.html So isn't this fixed?
Yes, it does look fixed to me. Closing.
Guys, the URL points to result from year 2003, some more recent URL is needed to prove that they are still running, imho. You can point me to more recent URL, but in case there is none, I am adding Petr Zajac to confirm that those tests are running daily.
You are right, that link is outdated, does not work now. The new link is http://ffjqa.czech/automatedtests/xtest/ (visible only from inside Sun). I couldn't find schema2beans tests in here, so this is not done. Changing to P2 task.
Obsolete milestone, please reevaluate