Skip to Content

Changes for page Testing-JUnit and TestNG

Last modified by Yana Oksner on 2026/01/08 12:10
From version 14.1
edited by Johann Werner
on 2023/11/13 11:58
Change comment: Renamed from xwiki:documentation.Testing-JUnit and TestNG
To version 15.1
edited by Yana Oksner
on 2026/01/08 12:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -How-tos
1 +documentation.Home.How-tos.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.jw
1 +XWiki.yanasd
Content
... ... @@ -64,19 +64,19 @@
64 64  
65 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 66  
67 -{{noformat}}
67 +{{code}}
68 68  
69 69  ${workspace_loc:MyEclipseProject/build/MyEclipseProject.framework}
70 70  
71 -{{/noformat}}
71 +{{/code}}
72 72  
73 73  For an application it should be (using the handy wolips_dir_loc variable)
74 74  
75 -{{noformat}}
75 +{{code}}
76 76  
77 77  ${working_dir_loc_WOLips:MyEcliseProject}
78 78  
79 -{{/noformat}}
79 +{{/code}}
80 80  
81 81  [[image:attach:RunConfig1.jpg]]
82 82  
... ... @@ -101,10 +101,10 @@
101 101  
102 102  That means that there will be no //build// folder in your project. In that case you must set the working directoy to the default:
103 103  
104 -{{noformat}}
104 +{{code}}
105 105  
106 106  ${workspace_loc:MyEclipseProject}
107 107  
108 -{{/noformat}}
108 +{{/code}}
109 109  
110 110  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.