APPS.CSK_DIAG_SOLUTION_PVT dependencies on JTF_DIAGNOSTIC_ADAPTUTIL

Line 171: tempInput := JTF_DIAGNOSTIC_ADAPTUTIL.initinputtable;

167: IS
168: tempInput JTF_DIAG_INPUTTBL;
169: BEGIN
170: -- If the Unit Test requires Input Parameters the defaults can be set up as follows:
171: tempInput := JTF_DIAGNOSTIC_ADAPTUTIL.initinputtable;
172: --tempInput := JTF_DIAGNOSTIC_ADAPTUTIL.addInput(tempInput,'DEMO VALUE','1');
173: defaultInputValues := tempInput;
174: EXCEPTION
175: when others then

Line 172: --tempInput := JTF_DIAGNOSTIC_ADAPTUTIL.addInput(tempInput,'DEMO VALUE','1');

168: tempInput JTF_DIAG_INPUTTBL;
169: BEGIN
170: -- If the Unit Test requires Input Parameters the defaults can be set up as follows:
171: tempInput := JTF_DIAGNOSTIC_ADAPTUTIL.initinputtable;
172: --tempInput := JTF_DIAGNOSTIC_ADAPTUTIL.addInput(tempInput,'DEMO VALUE','1');
173: defaultInputValues := tempInput;
174: EXCEPTION
175: when others then
176: defaultInputValues := JTF_DIAGNOSTIC_ADAPTUTIL.initinputtable;

Line 176: defaultInputValues := JTF_DIAGNOSTIC_ADAPTUTIL.initinputtable;

172: --tempInput := JTF_DIAGNOSTIC_ADAPTUTIL.addInput(tempInput,'DEMO VALUE','1');
173: defaultInputValues := tempInput;
174: EXCEPTION
175: when others then
176: defaultInputValues := JTF_DIAGNOSTIC_ADAPTUTIL.initinputtable;
177: END getDefaultTestParams;
178:
179: ------------------
180: -- currentUser

Line 315: JTF_DIAGNOSTIC_ADAPTUTIL.setUpVars;

311: IS
312: BEGIN
313: -- The Report for the Unit Test is represented by a CLOB
314: -- This CLOB must be initialized before it can be used
315: JTF_DIAGNOSTIC_ADAPTUTIL.setUpVars;
316: -- if the report is HTML-based, then the first string added to
317: -- the report must be "@html".
318: -- addStringToReport writes to the Report CLOB
319: JTF_DIAGNOSTIC_ADAPTUTIL.addStringToReport('@html');

Line 319: JTF_DIAGNOSTIC_ADAPTUTIL.addStringToReport('@html');

315: JTF_DIAGNOSTIC_ADAPTUTIL.setUpVars;
316: -- if the report is HTML-based, then the first string added to
317: -- the report must be "@html".
318: -- addStringToReport writes to the Report CLOB
319: JTF_DIAGNOSTIC_ADAPTUTIL.addStringToReport('@html');
320: JTF_DIAGNOSTIC_COREAPI.insert_style_sheet;
321: -- line_out writes to the Report CLOB
322: JTF_DIAGNOSTIC_COREAPI.line_out('======================================================');
323: -- BRPrint Adds a New Line to the Report CLOB

Line 336: report := JTF_DIAGNOSTIC_ADAPTUTIL.constructReport(l_statusStr, -- SUCCESS, FAILURE, WARNING

332: currentUser;
333: moveSolutionsTest;
334: ----------------------------------------------
335: -- Construct the Report with the corresponding Report Status information:
336: report := JTF_DIAGNOSTIC_ADAPTUTIL.constructReport(l_statusStr, -- SUCCESS, FAILURE, WARNING
337: l_errStr, -- The Error Message
338: l_fixInfo, -- fix suggestions
339: l_isFatal -- Fatal Error: "TRUE" or "FALSE"
340: );

Line 342: reportClob := JTF_DIAGNOSTIC_ADAPTUTIL.getReportClob;

338: l_fixInfo, -- fix suggestions
339: l_isFatal -- Fatal Error: "TRUE" or "FALSE"
340: );
341: -- Return the clob output report
342: reportClob := JTF_DIAGNOSTIC_ADAPTUTIL.getReportClob;
343: END runTest;
344:
345: END CSK_DIAG_SOLUTION_PVT;