Silk Test Feature Request

  1. SilkTest Workbench: Enhance Results Configuration Options

    When executing Visual Tests or .Net scripts in the Workbench; the following general options are available for configuring how Results are generated:

    Save results with a new run number.
    Append Results to current run number.
    Overwrite existing run number with new Results.
    Do not save this Result.

    As our Visual Tests are executed every night, we do not really need to save every single result; but they are obviously useful for debugging purposes, in the event that a test does fail.

    It would therefore be useful if some additional options were available; that allowed user to specify the number of…

    3 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 Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  2. SilkTest Workbench: Default BaseState Execution Option

    When recording Workbench Tests; please provide an option that allows the user to set the default behavior, in relation to BaseState execution. Currently this is enabled by default; and can be disabled by modifying the App Configuration settings in the start step of a Visual Test. However it would be better to have the option to change this behavior while recording.

    1 vote
    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 →
  3. Open Agent recorder does not pickup extended winclasses

    Currently when using SilkTest Classic and the Open Agent, the Open Agent recorder does not pickup extended winclasses that a user has defined in an include file. For Example:

    [-] winclass MyDomTextField:DomTextField
    [ ]
    [-] SetText(String sText)
    [ ] this.TypeKeys(sText)

    This results in a lot a manual work to redeclare window declarations with the correct winclass and this recording behaviour is not in-line with Classic Agent functionality, which would successfully use custom winclasses when recording.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Silk Test Classic  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 →
  5. SilkTest Workbench: Enhanced Verifications from Screen Preview

    When Inserting a Verification from Screen Preview in Workbench Visual Tests; the text property of a textfield is not exposed in the Test Logic Designer, even when visible in the screen preview image.

    The workaround is to Insert the Verification from the Application under Test. However as it takes significantly longer to add verifications this way; I would like to see this behavior enhanced so that all properties are available for selection, when inseting verifications from Screen Preview.

    1 vote
    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. Improve the warnings when deleting disabled steps in Visual Tests

    a. If someone tries to delete a live step that has child code (e.g. 'using' statements), SilkTest Workbench pops up a warning saying that deleting the step may affect the test.

    b. If the same step is disabled for testing and then the user tries to delete it while the step is disabled, Workbench does not warn them that there may have child code that will be affected by deleting this step.

    Regardless of why the step was disabled in the first place, if a warning is generated for situation (a) then a warning should also be generated for situation…

    1 vote
    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 →
  7. Improve the reporting procedures for SilkTest Workbench

    Provide a method for reporting on

    Total number of automated scripts
    Total number of steps across all tests run
    Total number of passed/failed verifications

    3 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 →
  8. DomButton Select method should verify if the button is enabled

    When calling a select method on a DomButton - the Select should verify whether the DomButton is enabled or not, if it is not enabled the Select should do nothing, if it is enabled, then the Select should be actioned then.

    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 →
  9. Silk Test Workbench: Option for hiding disabled steps in a Silk Test Workbench visual test

    When debugging a script, it is often useful to disable scripts. At times it would be helpful to be able to "hide disabled steps". This would let you focus your debugging efforts on which steps are functional. This is especially true for more complex scripts.

    1 vote
    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 →
  10. Workbench: Enhance Functionality when Inserting Control from AUT.

    When using 'Insert > Control From > Application under Test' in Workbench Visual Test; after choosing the control from the application, the user is prompted to select the method to be used with the object.

    I would like to see this enhanced with wizard-type functionality; that also prompts the user for any other parameters or keys required for the chosen method to work.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  11. Script modules to be referred to by id

    When you change a script name, you have to then go into every script which references the old script name and update the name. The scripts should be handled on an ID base so the name can be maintained at will.

    2 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 →
  12. put the parameter data file into the database server ...

    now the data is in the file system, due to security issue, most of client do not allow share folder.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Silk Test Workbench  ·  Flag idea as inappropriate…  ·  Admin →
  13. Silk Test: Ability to perform object recognition on changing attributes in the application under test

    Important: The ability to perform object recognition on changing attributes in the application under test. Customer wants to know how Silk Test will behave upon recognition of an object that has changed in the AUT- will it stop the test, or do a best guess and move on…

    - Request for Silk Test to have a way to identify objects that have had their attributes changed. The functionality should demonstrate the following:
    o The process of identifying objects that have changed during playback
    o The way that the changed objects are identified after play back
    o The process to update…

    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 →
  14. Definitions on right clicking function names

    Can we have the ability to navigate through code so when you right click a function name or variable the code jumps to variable declaration or function definition. And maybe also a way to get back, like we had in test partner.

    4 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 →
  15. 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 →
  16. Silk Test Workbench: Hot key for adding "Control From" during record time

    There is a way to add verifications during record time, but not to add "control from" during record time. This same screen needs to be available during record time, and there needs to be a consistent hot key for adding these while recording and not recording.

    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 →
  17. Per Incident 2644048: Allow ResExtract to show results for each sub-plan inside a master-plan.

    I can informed that this behaviour is currently as designed. It is not possible for ResExtract to extract results for each plan that is a sub-plan of a master plan because what ResExtract does is that it takes a res file and puts the contained data to a txt file. That means this will happen once a res file is available - so it cannot happen earlier. If a master plan is executed, a res file will not be available during the execution of the sub-plans in the master plan, therefore, no data will be extracted until the end of…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Silk Test Classic  ·  Flag idea as inappropriate…  ·  Admin →
  18. Provide a function that returns the user that executed a test in Silk Test Workbench

    Currently, it is not possible to get hold of the username of the user that executed a script as a string in either a VB.NET script or a Visual Test.

    This information is currently only available in the run result that would be created by the user that executed the script. This information is also present in the entries that are created in the Details tab of the result.

    Can we provide a function that returns the user that executed a test in Silk Test Workbench as string to a VB.NET script or a Visual Test.

    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 →
  19. Be able to call your own function when error happens

    In Test Partner you could have your own function get called when an error happens. Like this
    Dim oe As TOnError
    Set oe = OnError("ScriptErrorHandling.ErrorFunction")

    There really isn't a way of doing this in the new Silk Test 13.5 (with .net) the only option is to do a Try catch over your full script which is not reasonable. The funny thing is, the Visual Test has an option to put in an On error and to call an Asset or another Visual Test.
    Even the older Silk Test had a Do except which could be doable but not very practical. …

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. store more object attribute into the object repository

    If the object attribute has some minor change, no need to update the object repository or change the code.

    1 vote
    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 →
  • Don't see your idea?

Silk Test Feature Request

Categories

Feedback and Knowledge Base