BuyLog In
Ticket Q375513
Visible to All Users

CodedUI Extensions do not work

created 12 years ago

Cloned from Coded UI Test Extension FAQ
In regards to bulletin number "[8) I can't get your extension to work. What should I do?, ]", it indicates that "The minor version of the CUIT Extension must be the same as the minor version of the DevExpress WinForms controls used in your application or installed on a test machine. "

In that case, what is the recommended practice for this below scenario,
- Our organisation has Dev team and QA team co-exist independently
- QA team automates test cases to test the application in a separate process, separate solution from the dev team.
- In the beginning, both QA team and Dev team start with the same DevExpress version (i.e. v12.2.4)
- A bug found in the CodedUI extension package, which blocks the UI automation. (i.e. A control could not be reconized)
- A newer version of DevExpress fixes this issue
- QA team needs to upgrade to the newer version of DevExpress to benefit from the fix
- However, the Dev team is not in the position to upgrade DevExpress (there is a very strict process in that team to upgrade any 3rd party components).
- Then according to the pre-requisite (same version requirement) mentioned above, QA team will not be able to automate for the existing application after the upgrade.

Just wondering, is there a mechanism to allow the DevExpress CodedUI extension package to be back-compatible with older version of DevExpress applications? Without this mechanism, all the fixes dedicated to the codedUI automation will not provide much value until the application upgraded with the same version, which does not always happen timely. For instance, there is no reasonable justification to request the Application team to upgrade devExpress if the fix is only for the CodedUI extension package.

Sign in to comment on this post

Answers approved by DevExpress Support

created 12 years ago (modified 12 years ago)

Hi Chengwei,
Our Coded UI extension communicates with our controls via a special interface defined in the DevExpress.Utils assembly. Our controls implement that interface to provide information about them. In most cases, to fix an issue with Coded UI, it is necessary to change how controls implement the interface. Thus, to get a fix, it is necessary not only to have a new version of the extension assembly but new versions of assemblies with controls. As a result, it is necessary to update both our Coded UI Extension and our controls.
Would you please send us a project illustrating the issue you faced? We will do our best to find a workaround for the issue so that you won't need to update your current version.

    Comments (2)
    C C
    Chengwei 12 years ago

      Hi Gosha,
      Thank you for your clarification.
      I am in such a situation, our development team (another team in our organization), they are developing our product by using DevExpress v12.2.4; My team, the automation team is writing CodedUI test cases to test this product, and is also using DevExpress v12.2.4. As our QA team need to upgrade to version v12.2.11 to get the fix for ticket Q499753, and Q500095. and we have upgraded all the QA projects with this DevExpress version; However, our QA team does not touch the production code, (i.e. we are not in the position to upgrade production projects with the same version of DevExpress v12.2.11, and we are not allowed to just simply upgrade DevExpress to a newer version without extensive testing, which always takes a while). Therefore, if just only upgrade QA projects to the newer version, but not the production projects at the same time, we certainly get the the Extension version mismatch problem, please refer to the attached snapshot.
      I apologize for not being able to provide you a real project, as I don't have the sources for our production code; and I cannot simulate such a situation (product in version v12.2.4, but automation is with version v12.2.11), as my environment has already upgraded to the v12.2.11, and fortunately I don't have the luxury of keeping multiple version environments.
      It would be highly appreciated if you can help us workaround this situation.
      Regards,
      Chengwei

      DevExpress Support Team 12 years ago

        Hi Chengwei,
        In this case, I suggest you use the workaround provided in those tickets.
        From A cell value of a parent node is returned when parent and child nodes have the same index in the collection: add the required search configuration manually.

        C#
        node.SearchConfigurations.Add(SearchConfiguration.DisambiguateChild)

        From Coded UI cannot locate PopupMenuBarControlMenu on RibbonForm: a workaround is to change the UIMap file so that there were no additional windows between the PopupMenuBarControlMenu and UIItemWindow.
        If you still experience problems implementing any of these solutions, feel free to reactivate this ticket and post a project illustrating the issue.

        Sign in to comment on this post

        Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

        Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.