Skip to Content

Changes for page Testing-JUnit and TestNG

Last modified by Yana Oksner on 2026/01/08 12:10
From version 11.1
edited by Johann Werner
on 2012/08/06 03:19
Change comment: differentiation between normal and bundle-less builds
To version 10.1
edited by Johann Werner
on 2012/07/25 10:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -54,16 +54,9 @@
54 54  
55 55  == Minor configuration in eclipse ==
56 56  
57 -To be able to test your business objects layer in JUnit or TestNG test cases, you should set the following parameters in your test case/test suite launch configuration depending on if you are using //normal// or bundle-less builds.
57 +To be able to test your business objects layer in JUnit test cases, you should set the following parameters in your test case/test suite launch configuration :
58 +First in the //"Arguments"// tab, set your working directory to the build product of your project. For example, for a framework project the working directory should be :
58 58  
59 -=== Normal builds ===
60 -
61 -A //normal// build means that you have checked the build option //Generate bundles// within the WOLips preferences.
62 -
63 -[[image:bundle_builds.png]]
64 -
65 -First in the //"Arguments"// tab, set your working directory to the build product of your project. For example, for a framework project the working directory should be:
66 -
67 67  {{noformat}}
68 68  
69 69  ${workspace_loc:MyEclipseProject/build/MyEclipseProject.framework}
... ... @@ -83,30 +83,19 @@
83 83  Then, in the classpath tab, select the //"User Entries"// entry and use the //"Advanced..."// button and select the //"Add Folders"// button.
84 84  [[image:RunConfig2.jpg]]
85 85  
86 -Select the //"Java"// folder of your build product. Use the //"Up/Down"// buttons to move this folder at the first position of your classpath.
87 -[[image:RunConfig3.jpg]]
79 +Select the //"Java"// folder of your build product.
88 88  
89 -{{note title="Be Careful"}}
81 +{{note}}
90 90  
91 -If during your tests execution you see error messages such as *cannot cast EOGenericRecord to <your object>* please check that the _"Java"_ folder is at first position in your classpath entries.
83 +{color:#333333}If you are using bundle-less builds you don't have a build folder. You need to check the{color} {color:#333333}{_}Generate bundles{_}{color} {color:#333333}option in the preferences WOLips->Build and clean your project to get it generated.{color}
92 92  
93 93  {{/note}}
94 94  
95 -The last step is to add the parameter //-DNSProjectBundleEnabled=true// to your VM parameters.
96 -[[image:vm_arguments.png]]
87 +Use the //"Up/Down"// buttons to move this folder at the first position of your classpath.
88 +[[image:RunConfig3.jpg]]
97 97  
98 -=== Bundle-less builds ===
90 +{{note title="Be Careful"}}
99 99  
100 -A //bundle-less// build means that you have unchecked the build option //Generate bundles// within the WOLips preferences.
92 +If during your tests execution you see error messages such as *cannot cast EOGenericRecord to <your object>* please check that the _"Java"_ folder is at first position in your classpath entries.
101 101  
102 -[[image:bundleless_builds.png]]
103 -
104 -That means that there will be no //build// folder in your project. In that case you must set the working directoy to the default:
105 -
106 -{{noformat}}
107 -
108 -${workspace_loc:MyEclipseProject}
109 -
110 -{{/noformat}}
111 -
112 -On the classpath tab you don't need to add the //"Java"// folder of your build product so only the default classpath should be listed for the //"User Entries"//. Be sure to add the parameter //-DNSProjectBundleEnabled=true// to your VM parameters as for //normal// builds.
94 +{{/note}}