Hi everyone,
I downloaded yerstaday the testing framework (https://www.telerik.com/try/telerik-testing-framework).
And tried to use it today with a dotnet 6 wpf application and a dotnet 6 xunit test project and it seams that the testing framework has compatibility issues.
Can someone confirm it ?
1 Answer, 1 is accepted
Hello François,
I tested locally with .NET core 6 WPF application and Test Studio is able to record and execute tests against it. The issue in this case is caused by the target framework of the xunit test project, which is also .NET core 6. The Telerik Testing Framework works against .NET 4.5 due to limitations from some of the dependencies and our support for older versions of Visual Studio.
I created a public feature request on your behalf to increase the supported version of the test project and our product team will evaluate it further. You can add your vote and follow the public item to receive notifications where there is any activity.
In the meantime, you can create new test project that is targeting .NET 4.5 framework and try out the Telerik Testing Framework for your automation scenario.
Thank you for your cooperation and detailed posts.
Regards,
Plamen Mitrev
Progress Telerik
Does UI testing really fit into CI/CD?
If you want to find out how to take advantage of continuous delivery pipelines, join our Test Studio webinar on Wednesday, April 6 at 11 am EST | 5 pm CET.
Thanks for the answer and for the feature request.
Unfortunately Specflow is not compatible with .NET 4.5.
I turned my attention to test studio.
I understand that the clash of supported versions between Test Studio and Specflow is causing troubles. I hope that we can dedicate time to increase the supported version of .NET framework for test projects. That will allow you and other users to integrate Test Studio with other tools and frameworks.
Thank you for starting this discussion and for sharing details about the use case you have.
Hi Daniel,
It's great that you found the answer for some troubles you experienced.
Actually, the information about the supported target framework version for Test Studio project is listed in the system requirements page - you can check it here. But you are right that this might be not that clear and that it could be more visible. I'll note that down in the list for documentation improvements.
While on this topic I wanted to add that we are working on upgrading the target framework version, so you can check our future release notes for info on this.
Don't hesitate to contact the Test Studio Support team in case you have any further queries. Thank you for your cooperation!
Regards,
Elena
Hi Elena,
indeed the target frameworks for the Test Studio plug in itself are documented. And my written tests work with the newest version 4.8.
But I'm talking about the Test Runner. We started to run the tests I've written in VS with .NET Framework 4.8 in the test runner and it had a long list of compilation errors because the test runner is only supporting .NET Framework 4.5 with C# version 5.0. The test runners target framework isn't documented in your link.
So at the end the VS plug in is supporting higher .NET Framework versions than the test runner.
And I'm looking forward for the future update supporting higher framework versions.
Regards,
Daniel
Hi Daniel,
Thank tor following up on the topic.
Actually the projects in Test Studio targets .Net Framework 4.5.2 as a predefined setting, which cannot be changed. That means that all tests executed through the Test Studio engine - including the Test Studio Test Runner, use the 4.5.2 version of the .Net Framework.
The option for using higher version of the target framework is only available in Visual Studio projects, where you can change this.
I'm sorry to hear that this wasn't clear enough and will do my best to update the information on the documentation in more clear words.
Thank you for your cooperation once again.
Regards,
Elena
Hi François,
We recently release support for .net core 5 WPF applications and I tested that a demo WPF application with the following target framework also works. Can you tell me more about the application you want to automate? What is the target framework? Can you share a demo app for me to test?
<TargetFramework>net6.0-windows</TargetFramework>
Thank you for starting a discussion on the topic.
Hi Plamen,
enclosed is a sample project that produces the error on my machine.
Waiting for your feedback.