Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button.  The answer will now appear with a checkmark.  Please be sure to always mark answers that resolve your issue as verified.  Your fellow Community members will appreciate it!  Learn more.

  • State Verified Answer
  • Replies replies
    2
  • Subscribers subscribers
    8
  • Views views
    608
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to Import Silk Test Workbench Tool Scripts and Object Map to Silk4NET in Visual Studio?

Ambika Ma

I have created vb.net scripts in Silk Test Workbench tool. 

Now i have to migrate all the scripts and object map to Silk4NET in Visual Studio.

Silk Test Workbench Tool exports the scripts to zip file format and it couldn't be imported in Visual Studio Silk4NET.

I need to use already created vb.net scripts and object maps  from Silk Test Workbench tool to Visual Studio Silk4NET.

Is any way to directly import the Scripts and Object Map from Silk Test Workbench tool to Silk4NET?

  • Verified Answer

    +1  

    Hi

    Unfortunately it is not possible to export Silk Test Workbench assets directly to Visual Studio.

    You will need to manually copy the source code and Object Map assets to the relevant Silk4NET solution.

    Regards
    Robert

  • 0 in reply to   

    Hi Robert,


    Thanks for the reply.

    As per you comments, I have copied vb.net source code and object map assets from SilkTest Workbenck tool to Visual Studio SILK4NET.

    It were worked without any issues

    Thanks,

    Ambika

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.