Silk Performer Feature Requests

Please note: The Silk Performer feature requests portal has moved. Click here to access the Idea Exchange platform in the Silk Performer Community.

Existing ideas have been migrated, and you can still view ideas and comments in UserVoice for reference.
  1. Ignoring recorded fwait values on playback

    Allow on Playback of the recorded script the capability to ignore any fwait values without running the workload in stress mode. We understand the purpose of the fwait, but would prefer the default of 0.00 to be used without having to modify every fwait that has a value greater than 0.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow browser driven to record silverlight applications

    Allow browser driven projects to record silverlight applications. We are seeing more of these types of applications, and would be nice to be able to record them and do performance testing on them.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Show in any case in the Overview Report the available measurements

    After the load test was terminated with Kill All, although measurements are available, but are omitted in the Overview Report.
    Since the measurements are available, it would be very good to display this in the Overview Report.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. The ability to run a baseline test from the commandline is needed

    Be able to specify Baseline as the workload for the command-line argument and have the tool run a baseline test.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Option to Extend Acceptable Attribute Value with Browser Driven Recording in Silk Performer

    During a BDLT recording, it seems that the acceptable max value length for an attribute is 20 characters long, if the value supersedes this length the recorder will move on and select another attribute as part of the XPath Locator.

    A feature which increases the acceptable length of a value for an attribute during record would be beneficial, for example SilkTest have the ability to edit the following:

    OPTXBROWSERLOCATORMAXATTRIBUTEVALUELENGTH

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. .Net Explorer doesn't support for passing optional parameters to C# methods

    Currently Silk Performer 9.0 doesn't support passing optional parameters to C# methods. When I call methods without optional parameters, it throws exception "Missing Method" and when I pass all parameters it works fine. I strongly recommend Micro Focus to implement this feature.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →

Silk Performer Feature Requests

Categories

Feedback and Knowledge Base