Silk Test Feature Request

  1. The properties of result step should include the value of st_LastReturnValue

    When using the results file to debug a Visual Test execution, there are often no details returned with regards to the value returned from methods that retrieve information from a control, e.g.:

    - GetMultiText
    - Exists
    - IsFocussed

    It would be beneficial if the result step details also included the value of st_LastReturnValue. For example, if a user wanted to check whether an Exists call returned True/False an additional step would be required to log that information to the results.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  2. Silk Test: Support for Gupta:ChildTable control

    Provide support for Gupta:ChildTable controls.

    You can find background on the control type from http://www.guptatechnologies.com/ developed in Centura Programming Language.

    We have tried unsuccessfully to class map the control to a standard class.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Silk Test Workbench - Ability to clean up database by removing unused assets

    My application has evolved, many buttons and images which I used to interact with no longer exist.

    The Visual Tests which interacted with these objects have now been removed as the tests are no longer relevant.
    My customer has the following issue:-

    New object map entries have now been created for the evolved application, to replace the buttons and images which no longer exist in my application.

    There are now many obsolete entries in the object map which I no longer require.

    The existing “Purge Asset Version” feature is not suited to my scenario as I have a single object…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  4. SilkTest Workbench: Enhanced 'Condition Designer' options

    Most of our automation scripts are created as Visual Tests; and for a number of reasons do not like to use Application Configurations and Object Maps in our projects.

    With this type of approach however; it is difficult to create the type of decision logic that we need, because we cannot enter full XPath queries in the Value field of the condition designer.

    For example; if I wanted to test that a dialog button exists on screen, and run a child test if this returns True; I would like to enter the following Xpath for Value1 in the Condition Designer:

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  5. Scroll breakpoint to centre of page when debugging .Net Scripts

    In SilkTest Workbench when a user sets a breakpoint and runs their test - when the breakpoint is reached Silk Test returns to view, but the breakpoint line is scroll up off the screen, the breakpoint line is obscured by the modules and functions dropdown menus at the top of the script. The user would like to have the breakpoint scrolled to the centre of the screen or perhaps to the top, but under the two dropdown menus. (SI 2780346)

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide an index locator attribute similar to the Classic Agent Index tag

    If testing localized versions of an application, an "index" locator attribute similar to the Classic Agent index tag would be useful as an alternative way to identify controls.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Silk Test Classic  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide a native function to get text from a dynaically generated AJAX table

    Currently when an AJAX table is dynamically generated each cell has the same set of identifiers. As long as you know what text you want to verify, you can navigate around the table by columns and rows and use text recognition to compare the contents of each cell. Can this be compacted into a native call e.g.

    getDynamicCellText(x,y)

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. When in debug mode - SilkTest always shows the local variables window - make this optional

    When seting a breakpoint and running a .Net script in debug mode - SilkTest always shows the local variables window.
    The customer would like to have this as an optional window - where they can select if they want to see this or not when debugging. (SI 2780347)

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow the ability to natively identify JRadioButtons inside a JTableCell

    Currently the only way to action a JRadioButton inside a JTableCell is to use the co-ordinates parameter of ClickCell().

    Requested from SI 2590427

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Object map entries not used in existing Visual Tests for a project should be easily removed.

    My application has evolved, many buttons and images which I used to interact with no longer exist.

    The Visual Tests which interacted with these objects have now been removed as the tests are no longer relevant.
    My customer has the following issue:-

    New object map entries have now been created for the evolved application, to replace the buttons and images which no longer exist in my application.

    There are now many obsolete entries in the object map which I no longer require.

    The existing “Purge Asset Version” feature is not suited to my scenario as I have a single object…

    0 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 →
1 2 3 4 5 7 Next →
  • Don't see your idea?

Silk Test Feature Request

Categories

Feedback and Knowledge Base