You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/developing/testing/configuring.mdx
+42-43Lines changed: 42 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,50 +189,49 @@ Here is an example with all execution parameters set in the `testing.json` file:
189
189
</TabItem>
190
190
</Tabs>
191
191
192
-
<Asidetype="note">
193
-
The `wrapperCmd` parameter in the `RUCRTRPG`/`RUCRTCBL`/`RUCALLTST` specifications are not actual parameters of the RPGUnit commands, but rather are provided by the extension to allow wrappering them. This is primarily used when integrating RPGUnit with other vendor tools.
194
-
195
-
**Example `testing.json` configuration**:
196
-
```json
197
-
{
198
-
"rpgunit": {
199
-
"rucrtrpg": {
200
-
"tgtCcsid": "*JOB",
201
-
"dbgView": "*SOURCE",
202
-
"cOption": [
203
-
"*EVENTF"
204
-
],
205
-
"wrapperCmd": {
206
-
"cmd": "MYLIB/MYCMD TSTCMD",
207
-
"params": {
208
-
"desc": "My description"
209
-
}
192
+
### Vendor Integration
193
+
The `wrapperCmd` parameter in the `RUCRTRPG`/`RUCRTCBL`/`RUCALLTST` specifications are not actual parameters of the RPGUnit commands, but rather are provided by the extension to allow wrappering them. This is primarily used when integrating RPGUnit with other vendor tools.
0 commit comments