Reputation: 2680
aI am interested in automating some application / system level tests on an existing product range. Our product range consists of several distinct applications, written in .Net 3.5 and using WPF for the presentation layer.
Ultimately, I am interested in finding an application testing suite that is capable of executing scenarios and reporting results. I would like some way to define/record the scenarios, and see which scenarios passed/failed testing.
I do not have any experience in the area of automated application testing. Is anyone able to recommend a testing suite?
Upvotes: 4
Views: 7612
Reputation: 1
I recommend several automated testing suites for your .Net 3.5 and WPF-based applications.
Microsoft Visual Studio Test Professional: This is a comprehensive testing suite from Microsoft that is integrated with Visual Studio and can be used for automating application tests. It includes features such as test case management, test execution, and reporting.
Telerik Test Studio: This is a testing suite that provides a visual interface for defining and executing tests, as well as reporting results. It also includes features such as load testing and performance testing.
NUnit: This is a popular open-source testing framework for .Net that can be used for automating unit and integration tests. It includes features such as test case management and test execution, and can be integrated with other tools such as Continuous Integration systems.
Automated UI Testing with White: This is a .Net library for automating tests of WPF-based applications. It allows you to write code that interacts with the user interface of your applications, and can be used for both functional and regression testing.
These are just a few of the automated testing suites available for .Net and WPF applications. The right choice will depend on the specific needs of your product range and testing requirements.
Welcome my channel: https://www.youtube.com/channel/UC8cggrSfpRTfjxpvvlDH6Gg
Upvotes: 0
Reputation: 61
If you're willing to put in the work, I have found the White Framework, which is built on the Microsoft UI Automation API (supports WinForms, WPF & Win32), to be the most flexible and customizable approach. I have used to develop a GUI automation test suite of over 2500 tests (>12 hours run time).
The White Framework can also be integrated into either NUnit or MSTest.
Upvotes: 1
Reputation: 4588
Visual Studio 2010 includes a new product for doing GUI testing. Test Manager 2010 is included in Visual Studio 2010 Test Professional and Visual Studio 2010 Ultimate and enables recording and playback of actions in GUI applications as well as rich reporting.
The tools integrate with Team Foundation Server 2010 to store test cases, test runs and log bugs that are found during testing.
This blog post (eventually!) includes an overview of the testing process and tools in Visual Studio. Focus on the Testing Workflow and have a look at the included videos for more information.
Upvotes: 1
Reputation: 15802
Some other frameworks -
White UI Test framework:
TestApi - a library of Test APIs:
XAML Compliance Suite V1:
Also have a look at these articles -
Automating UI Tests In WPF Applications:
and WPF Application Quality Guide:
http://windowsclient.net/wpf/white-papers/wpf-app-quality-guide.aspx
and a similar question on stackoverflow also have some more links -
How to test a WPF user interface?
Upvotes: 5
Reputation: 3109
I would avoid the record and playback systems because they produce fragile tests. These systems seem ok until you change the app, and you're forced to recode your tests.
A newer and more agile friendly approach is in tools like IcuTest (http://www.IcuTest.com/).
Upvotes: 1
Reputation: 1024
I use QTP. It's nice, but expensive. Selecting a tool depends on amount of money that you can spend.
Upvotes: 1
Reputation: 11601
Please try Test Complete http://www.automatedqa.com/products/testcomplete/top-reasons-to-try/
Upvotes: 2
Reputation: 1974
NUnit is the generally accepted best .NET unit tester. In terms of integration testing etc, not sure about that.
If you want to test your WPF applications, pretty much the only way is to use MVVM. Separating out the view data from everything else allows you to unit test dummy view's. If you haven't done this already it's probably not worth it, since it's such a large architectural change.
Upvotes: 0