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.
build :- gfesb v2.2 20091004-0736 Order specified in the selected-tests.properties file is not taken. By default Alphabetical order is taken. Steps :- 1) Import attached project or similar project which has multiple test cases . Rename the test cases in non-alphabetical order. 2) change the order of execution to some non-alphabetical order. i.e. TestCaseAdd,,TestCaseUpdate,TestCaseSearch,TestCaseDelete 3) Deploy and Run the project in batch. 4) Notice that the tests run in alphabetical order and not in the order specified in selected-tests.properties open the selected-tests.properties after execution. it is reverted back to Alphabetical order and tests fail because of this bug. http://mostral.sfbay.sun.com/jtr/2_6_0/linux/drain/0923/oracle/gfesb_oracle.shasta/qajbi.Linux.i386/ldapbc_LDAPMultiOperations/
The test cases are ordered because of an old issue that duplicate test case names were put into the selected-tests.properties file. Will remove the existing test case reordering.
I thought you were complaining about command line testing, where there was a bug but was fixed a long time ago. Inside NetBeans, when you invoke the Test action from the CompApp node, it always regenerates the selected-tests.properties by populating it with all test cases. This is by design since there is no UI support for the selected-tests.properties file. Currently, the only way that you can specify test order is by selecting the test case individually in the desired order and invoke the Run action.
The same test used to work in CAPS 6.2 build ,(netbeans 6.5 ) ldapbc/ldapbc_LDAPMultiOperations (pass) 2009-06-26T18:10:58.50 2009-06-26T18:11:48.44 Please check the runs here :- http://mostral.sfbay.sun.com/jtr/2_5_1/nt/zambia/0626/oracle/caps_oracle.shasta/tonga.output/Summary.html The order specified in the selected-tests.properties was Add, Update, Search , Delete and it used to execute accordingly. With the above justification I feel this is a defect still.
Verified in the build 20091011-0735 , the issue is not present. but there is no UI support for the selected-tests.properties file. Hence marking this as an enhancement request and not a defect.