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 41356 - Move ValidateLayer*Test to ide/test/qa-functional/ or to general build harness
Summary: Move ValidateLayer*Test to ide/test/qa-functional/ or to general build harness
Status: NEW
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: pgebauer
URL:
Keywords: TEST
Depends on:
Blocks:
 
Reported: 2004-03-25 15:29 UTC by Jesse Glick
Modified: 2015-09-09 11:22 UTC (History)
4 users (show)

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2004-03-25 15:29:17 UTC 
These are not unit tests at all; they are testing
the IDE as a whole, so they should be moved to the
same place as other IDE functional validation tests.
Comment 1 Jaroslav Tulach 2004-03-25 15:36:03 UTC 
Ok, I will move them to ide and merge them with "clicking" validation
tests, so the IDE starts only once during commit-validation.
Comment 2 Jaroslav Tulach 2005-04-05 08:26:39 UTC 
From issue 55077, by jglick: 
  
ValidateLayerJavaHelpTest.java should not be in core/javahelp/test/unit/src; 
it 
should be in ide/test/qa-functional/src. It is not a unit test of the JavaHelp 
API; it is a functional test of the complete IDE build. (Yes I know there are 
ValidateLayer*Test.java in core/test/unit/src but those should be moved too, 
we 
just haven't gotten to it yet.)
Comment 3 Jaroslav Tulach 2005-05-19 14:25:39 UTC 
There validation tests should probably be moved to harness as they are 
valuable for everyone building on top of NetBeans platform. Do you want to do 
it Jesse? If not, then please suggest where could in your opinion be the right 
place and reassign back.
Comment 4 Jesse Glick 2005-05-19 15:31:03 UTC 
Interesting idea. For that I might want to convert them to Ant tasks though.
Comment 5 Jaroslav Tulach 2005-05-23 12:31:01 UTC 
Ant tasks are ok, but they will need access to various NetBeans APIs. So 
either you put all of these APIs on the ant task classpath or you create a ant 
task that will start the NetBeans and then execute validation actions provided 
by real modules. 
 
I would suggest to provide: 
 
ie org.netbeans.modules.apisupport.Validate { 
  public String getName (); 
  public void validate () throws AssertionError; 
} 
 
which could be registered into META-INF/services by various modules and which 
would then do the actual verification. The ant task would just start the IDE 
in nongui mode and checked for all Validate objects and reported 
success/failure.
Comment 6 Jesse Glick 2011-03-15 22:16:46 UTC 
Relevant to recently discussed ideas for aggregating AU from multiple binary sources - would like to run some sanity checks on resulting applications.