Absent Member.
Absent Member.
2151 views

SilkCentral Result Display

Jump to solution

Hi

Currently we are using SilkCentral to execute SilkTest Workbench scripts. Because we implemented our own keyword-driven framework (we are using version 15.5), all the keywords scripts are called by using reflection on the keywords written in spreadsheets.

Because we are using self-developed reporting tool, in Workbench settings we disabled all the reporting outputs, thus in SilkCentral all the tests are shown as failed even though actually tests passed. We want to customize SilkCentral result by creating an output.xml file (by following this page: http://community.microfocus.com/borland/test/silk_central/w/knowledge_base/13023.how-to-run-python-scripts-from-silk-central-test-manager.aspx). However it doesn’t work and still shows the same error message. It seems the newly created output.xml file is not picked by SilkCentral or is overwritten by the one generated by the server.

Is there any way to overcome this?

0 Likes
1 Solution

Accepted Solutions
Absent Member.
Absent Member.

Hi lei.wang,

Unfortunately the way you are executing the script this would not be possible to generate an output.xml and use this to process your results for a test passing or failing.

One option would be to run the tests as a ProcessExecutor script and start the workbench scripts from command line using the stw.exe process.

You can find more information about that here: documentation.microfocus.com/.../GUID-3D420342-BC7F-4C91-B5D5-6CEE27015790.html

You could then generate the output.xml file at this stage and upload it to SCTM_EXEC_RESULTSFOLDER. This would then be processed with your test to record results.

The SCTM_EXEC_RESULTSFOLDER is an environmental setting which is declared at runtime which can be used to add files to the Results Folder from your Argument List or Batch file.

If you want more information about running process executor scripts you can find this here: 

http://documentation.microfocus.com/help/topic/com.microfocus.sctm.doc/SCTM-179DFA5D-CONFIGURINGPROCESSEXECUTORTESTPROPERTIES-TSK.html

If you have any further questions let us know.

Regards,

Matthew

View solution in original post

0 Likes
2 Replies
Absent Member.
Absent Member.

Hi lei.wang,

Unfortunately the way you are executing the script this would not be possible to generate an output.xml and use this to process your results for a test passing or failing.

One option would be to run the tests as a ProcessExecutor script and start the workbench scripts from command line using the stw.exe process.

You can find more information about that here: documentation.microfocus.com/.../GUID-3D420342-BC7F-4C91-B5D5-6CEE27015790.html

You could then generate the output.xml file at this stage and upload it to SCTM_EXEC_RESULTSFOLDER. This would then be processed with your test to record results.

The SCTM_EXEC_RESULTSFOLDER is an environmental setting which is declared at runtime which can be used to add files to the Results Folder from your Argument List or Batch file.

If you want more information about running process executor scripts you can find this here: 

http://documentation.microfocus.com/help/topic/com.microfocus.sctm.doc/SCTM-179DFA5D-CONFIGURINGPROCESSEXECUTORTESTPROPERTIES-TSK.html

If you have any further questions let us know.

Regards,

Matthew

View solution in original post

0 Likes
Absent Member.
Absent Member.

Thanks Matthew, it's been helpful!

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.