I just added a Silverlight Unit Test Application (project) to my Solution to test my SL4 App.
Also added a Silverlight Test Class to that same project and created a simple test.
I'm using SL4, VS2010 and TFS2010 automated builds.
I'm not being able to associate that test to one of my test cases. Any reasons why?
Though, the associated automation test window detects unit tests belonging to a standard SL4 Test Project (included in the same solution).
Thank you,
Nuno Senica
Read the follow - article
Seems it should help you..
Pay your attention to Silverlight Unit Test Framework too.
Related
I have a ASP.net core web application and want to use Citrus framework for integration testing. All the documentation resources say it is meant for JAVA applications. Even an XML based test presentation requires a Java executable test class to run.
First of all is this possible to achieve?
Second, if it is possible, could someone guide me to the right steps to achieve this.
Thanks in advance.
Yes, it is possible to use Citrus Framework for testing application written in languages other than Java. However, the Citrus test cases has to be executed in an Java environment.
What this mean is that you probably want to keep Citrus tests in a Java project separate from your .NET application.
Orchestrating the start and stop of the .NET application before and after the integration testing could however be quite tricky. But even if you don't solve that, Citrus Framework would still be useful for you when developing and executing against your local .NET development environment.
I have a hard time figuring out how you actually do integration tests
Is it still automated test with JUnit, NUnit or whatever, or is it just using the program (it has a gui) an making sure that everything works?
You can refer what-kinds-of-tests-are-there and whats-the-difference-between-unit-functional-acceptance-and-integration-test
GUI testing can be listed in system testing, acceptance testing.
GUI test tool mostly depends on type of UI (Web/Desktop/Mobile). e.g. for web testing you can evaluate good open source tools like selenium.
How do I define an entry point for a project that has nothing but nUnit tests?
I have a bunch of nUnit TestFixture() classes that instantiate classes that return SQL data. The TestFixture classes have TestFixtureSetUp that contain all the parameters they need to instantiate the classes they’re using for tests.
I can run Unit Test Sessions in ReSharper, but I need to run the project in Debug and the entry point I have is a Windows Form. So how do I kick off and debug the tests? I thought nUnit had a test list that would fire the tests in order... Do I need an nUnit test constructor? so this is either an entry point question or an nUnit test list question.
Thanks!
How do I define an entry point for a project that has nothing but nUnit tests?
You don't. A test project is typically compiled as a library (DLL), not an executable, which means it doesn't require an entry point.
Instead of executing the project as an exe, you should just debug the tests. This is often done, when using nUnit, by attaching the debugger to the nUnit process then running the tests. However, tools like TestDriven.Net will simplify this further by allowing you to directly debug from within Visual Studio. Given that you're using ReSharper, you should be able to choose to debug from within Resharper as well.
So I'm looking to bring web application testing into our .Net environment with a framework such as Selenium. At first, it'll probably be the developers writing the tests, but later it may be just the QA team. I'm wondering where the tests should actually live. Should they live in the same solution that the web application lives or should they live in a completely separate solution that is just for the tests? Please, note these are regression tests that will be done via automating a web browser so access to the web app's assemblies is not required. The answer probably is based on the environment and other factors, but I'm curious about what other people have done in this situation.
Regression Testing covers both Unit and Functional Tests. Functional tests exercise the complete program with various inputs. Unit tests exercise individual functions, subroutines, or object methods.
Unit Tests are part of the solution's code and should live with the Primary Code as with Microsoft MVC. Since Functional Tests examine the whole system and not just components, they can live anywhere. However, since your Functional Test are automated scripts, they should be included inside the solution.
The advantage to having both Functional and Unit tests live with the code is the issue of project management. Having all project related files in one repository links code version with test version. Testing scripts need to be stored in a repository (version control system) just like any other project code, so it is good to keep them with the solution.
That way the test team can do white box testing (testing with access to code) by checking-out the solution just like a developer. Their work can be saved, shared, and documented inside Visual Studio. Microsoft even includes some web based management tools with Team Foundation Server that can be used for managing the testing with open communication between test team and developers.
I am looking at some options for using a web automated framework. I have so far looked at Selenium and Web Test (part of Visual Studio), Web Test does not test any client side code, so that kind of rules that one out. Selenium has most the features needed although I need to generate the .NET code for the tests, so that I can run the tests under TFS build server.
Is selenium the best automated testing web framework, or is there anything else worth looking at that could integrate with .NET and the TFS build. Ideally I want minimal code changes if any.
Appreciate your thoughts
Cheers
I've been constantly frustrated with Web Test in Visual Studio, though I'm not sure I understand what you mean when you say it can't test client side code.
For developer community support, ease of use, and cross platform access, I'd say Selenium is the hands down winner for programmatic browser automation. Selenium 2 works on every major OS/browser and even mobile.
I've tried WaitN and found some bugs in recent version of IE. There was a recent 2.0 release that has probably worked things out, but there are so many more people using Selenium it's worth relying on that community.
Selenium can generate C#. You can use the Selenium libraries in a C# class to create a web UI test library. Selenium is probably the most common tool.
Another option is WatiN, which is a descendant of Watir for .NET. It's another web UI automation library
This StackOverflow thread discusses using the two to test ASP .NET webforms, and might give you a good set of concepts to start from. My experience with the two is that they were both nice. I would go with Selenium if working with non-programming testers due to its great record-and-playback tools (for Firefox), and WatiN if working with SDETs / developers due to its richer libraries. When in doubt, Selenium is more common and more frequently used.
I've been using Selenium 2.0 (the C# bindings in particular) / NUnit / Hudson. Works well, and Selenium 2.0 is constantly improving and working out the remaining bugs