Test Automation

Welcome to the Test Automation product ideas page


Test Automation is an automated UI testing toolset that includes products for HP & IBM testing suites across the Windows Forms & WPF platforms.

Go to the Product Page
Get Help on the Forums

Help us improve our Testing Tools by telling us what you’d like to see in future releases!

Learn more about a status.

How can we improve Test Automation?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. method to return currrent version of TA in use

    We can use object.GetType().Assembly.FullName to get information about an object and what version of TA is being used.

    We plan to test different versions of applications that require different TA versions as well.

    It is easy for a user to forget to change the version before running the script.

    I would like a method that is not object based.

    It could be something such as TA.status

    Thanks,
    Kevin

    1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  Flag idea as inappropriate…  ·  Admin →

      This is fully implemented in TA-WPF in 14.2. A property called IGStatus. Which lets the user know what if any compatibility issue there are. It will also record with the status as NoAction followed by a comment of the IGStatus value if any compatibility issues are identified, and replay with a trappable error stating IGStatus in the error text.

      What IGStatus will let the user know is if a compatibility error is found, what version TA is as well as what version NA is, if the same version, but different CLR it will state the difference, or if one is versioned and the other is versionless.

      For the WinForms version of this it is a bit trickier as it is a more mature product that changed and improved as QTP\UFT improved, but will take more time and testing to verify the resolution is sound. But as of…

    • Ability to change TA version for mulitiple applications.

      Ability to switch the version of Test Advantage from inside of QTP/UFT.

      1 vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  Flag idea as inappropriate…  ·  Admin →

        The resolution for this will not be that you can switch versions mid script, which is not currently possible for us to do, but have multiple versions loaded at one time. This will allows you to in a single recording bounce between screens with different versions of the control without changing scripts or config files.

        Essentially the issue is QTP\UFT identifies our UI controls with the swfconfig.cfg file, which is an xml file that when initially designed only idenified UI controls by their full type name. As our controls do not change thier name from version to version, one version can be mistakenly loaded in place of another version which inevitably causes a conflict. We worked a resolution with QTP on this, allowing us to embed the dll name into the type identifier, or the fully qualified name. For example:

        Normal – Full type name only

        Name with…

      • Don't see your idea?

      Test Automation

      Feedback and Knowledge Base