Jean-Francois

My feedback

  1. 50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jean-Francois commented  · 

    Please, give us a way to manipulate the scripts out of SilkTest Workbench!

    From Frank Borland :

    Keep it open. I know you own other tools, and Borland never wants to restrict their use, or force you to change. So we make testing software that works seamlessly with what you already own. Borland leads the way in creating open, agile software today; I want to help that to continue and even improve in the future

    Jean-Francois commented  · 

    Yes! I put 3 votes.

    This is such a vital feature because SilkTest Workbench stores its script files into a database row. There is no way to easily manipulate the files. They are more or less locked inside the SilkTest Workbench environment. Even using the Export Assets feature, the files are not transformable because they are exported as XML with the actual text encoded in Base64.

    Currently, we use a home-made AutoHotKey (http://www.autohotkey.com/) script to automatically open each SilkTest script and extract the content into a text file. Then we use sed (http://en.wikipedia.org/wiki/Sed) on the whole collection of text file to do our replacement. Finally, using AutoHotKey again we automatically open each SilkTest script and copy-paste from the modified text file. All that is done semi-automatically, but it still takes a few hours!

    We have this semi-automatic process and going from SilkTest 2010 to SilkTest 13 was a pain because of a few changes we were forced to do.

    It would be really useful if there was a built-in way to do a Search and Replace (supporting regex please!)

    Jean-Francois supported this idea  · 
  2. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Silk Central Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →

    Ongoing review of the administration area of Silk Central – with review of email notifications.

    With the introduction of Clients within 12.1 this allows for there to be seperate administrators for each client and only the superusers within the clients projects will be notified of activities.

    We will add you comments to our backlog and the existing user story.

    Jean-Francois supported this idea  · 
  3. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Silk Central Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →

    Silk Central 17.0 has had multi select, keyboard navigation and drag and drop introduced. Drag and drop available within the assignment of tests to requirements, requirements to tests, execution planning. Work will continue in next release to expand this within the tool.

    Each release of SIlk Central we review the UI aspects of the tool. The request for extending the drag&drop capabilities through the tool is on our backlog for inclusion in a furture release. At this point however we are unable to confirm the exact release but will update you when we can confirm this.

    Jean-Francois supported this idea  · 
  4. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Silk Central Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Jean-Francois supported this idea  · 
  5. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Silk Central Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    Jean-Francois supported this idea  · 
  6. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jean-Francois supported this idea  · 
  7. 81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
  8. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Silk Meter Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    Jean-Francois supported this idea  · 
  9. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Silk Test Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    Jean-Francois supported this idea  · 
    Jean-Francois commented  · 

    Just as a note, I got this response :

    "We have reviewed this issue further and determine that this is more of an enhancement than a defect. Development will be reviewing this enhancement further."

    Jean-Francois shared this idea  · 
  10. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Silk Test Feature Request » Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
    Jean-Francois supported this idea  · 
    Jean-Francois commented  · 

    I reported this as a bug for SilkTest 2010 to supportline. Can't believe this obvious bug is still not fixed. So I'm going to give you one vote even tough it doesn't bother me much anymore. I'm now an expert trained into furiously mashing the ALT+F12 buttons whenever I need to stop a driver script!

    Incident - 2523400 -SilkTest Workbench: ALT+F12 Hotkeys terminate running test only - Driver test continues to run. 15 Jun 2011. Reproduced behaviour in-house and logged to R&D as potential defect - development see it more as an enhancement. Not sure I agree but RFE: 1079923 was logged to change/improve this behaviour in a future release. This RFE will remain open until addressed by R&D; but closing this incident pending

Feedback and Knowledge Base