Agile development and software thingies
Archive for the ‘C#’ Category.
Our open source MsSql UnitTest framework Slacker and SlackerRunner was featured on Microsoft Channel 9. Now it’s easier than ever to UnitTest your database and add it into your CI,CD build pipeline.
Watch Eric Kang from Microsoft explain in detail what you need and how it works.
I needed to add Nlog tracing that must be configurable from the config file. Finding a simple sample took a me a while. Therefor I’m putting the needed pieces here.
App.config
<variable name=“appName” value=“sample” />
<targets async=“true”>
<target xsi:type=“File”
name=“default”
fileName=“sample.log”
keepFileOpen=“false”
DeleteOldFileOnStartup=“true”
/>
</targets>
<rules>
<logger name=“*” writeTo=“default” minlevel=“Info” />
</rules>
</nlog>
</configuration>
And then in code, you can just do the following.
Things have changed a bit since the DNX .Net WebApi Integration testing post that I wrote about a year ago. This post will show updated code for .Net Core 1.1, I’m using the TestHost library as before.
I’m using these Nuget packages
xunit 2.3.0-beta1-build3642
Microsoft.AspNet.TestHost 1.1.1
Here is the UnitTest itself
namespace DevOps.Notes.Web.Spec
{
public class ValuseControllerTest
{
[Fact]
public async void PingTheServerRepeat()
{
// Setup client & server
TestServer server = new TestServer(new WebHostBuilder().UseStartup<Startup>());
HttpClient client = server.CreateClient();
// Make a request and check response
var getResponse = await client.GetAsync(“api/values/”);
var response = await getResponse.Content.ReadAsStringAsync();
TraceLog.Log(“web api, response=” + response);
// Hit the webapi, repeatedly
Stopwatch watch = Stopwatch.StartNew();
for (int i = 0; i < Util.Repeat; i++)
{
getResponse = await client.GetAsync(“/api/values/”+i);
response = await getResponse.Content.ReadAsStringAsync();
}
watch.Stop();
TraceLog.Log($“WepApi, round trips ={Util.Repeat}, Execution time, millisec={watch.ElapsedMilliseconds}, average roundtrip=” + ((double)watch.ElapsedMilliseconds / Util.Repeat));
TraceLog.Log(“web api, response=” + response);
// Done, release resources
server.Dispose();
client.Dispose();
}
}
}
As TFS vNext currently doesn’t have NoShadowCopy option ( should be coming with the new DNX / 2016 ). I had to modify my new TFS build definition to use xUnit runner to run my tests and then have it output the result file in the optional xunit xml format ( -nunit option ). However true to form TFS 2015 doesn’t understand the Nunit xml format even though they have that as one of their options on the UnitTest results upload vNext task. The next part was to figure out how to transform the Nunit xml to TRX in order for TFS to be able to show the results on the dashboard. Using nxslt3 to transform and NUnitToMSTest.xlst transformation seems to be the way to go. However NUnitToMSTest.xlst doesn’t transform it correctly, at least not to the liking of VS2012, VS2015 or TFS 2015. So I had to modify the xlst slightly and then it will load in VS and the TFS dashboard. Below is the new version of NUnitToMSTest.xlst.
New version
NUnitToMSTest.xslt
A lot has changed since my last post using Selenium to test web pages. Then you had to install a few things both on the client, browser and server. Today it has been simplified a lot. All you need really is the webdriver and you are in business. You can use the webdriver on your development machine and the server machine as well to run the Selenium tests. In my case I’m using the Ghost-PhanthomJS webdriver as I need to do headless testing ( no GUI ). Since it’s a lot harder to run tests automatically on the server if there is need for GUI, it will complicate things a lot, has to do with security restrictions etc.
Lets take a look at what is needed.
Create a new C# project in VS
Install xUnit Package Manger Console in VS using nuget.
Note I’m specifically using 1.9.2 and 2.0 as I know these two work on the build machine, I had trouble with other version combinations.
PM> Install-Package xunit -Version 1.9.2
Install xUnit VS Runner
PM>Install-Package xunit.runner.visualstudio -Version 2.0.0
Install the Chrome webdriver and libraries
PM> Install-Package WebDriver.ChromeDriver
Install the PhantomJS headless driver and libraries
PM> Install-Package PhantomJS
Then we write the test that will run after the build does the web deployment to the local server. The sample below just loads google.com and checks for the title, then shuts down.
namespace IntegrationTesting
{
public class HelloIntegration
{
// Proofs that google can be pulled up in the browser and has the right title
[Fact]
public void GoogleCheckTitle()
{
// Init
IWebDriver driver = new PhantomJSDriver();
// Test
driver.Navigate().GoToUrl(“http://www.google.com”);
var wait = new WebDriverWait(driver, TimeSpan.FromSeconds(3));
var title = driver.Title;
// Proof
Assert.Equal( “Google”, title);
// Close down
driver.Quit();
}
}
}
If you are using TFS you also need to point your build agent to the xUnit runner, in my case I just check it in as part of the project and set it like that.
Path to custom test adapters
$(Build.SourcesDirectory)\TestWebSite\xunit_runner\
That’s all you need, then you can write your own tests to test specific functionality tailored to your needs. Selenium is pretty powerful for Integration testing.
I started getting the following error when running specific UnitTests on the server, and only on the server. Running the tests from Visual Studio both using msTest and TestDriven was fine. But obviously something was missing. The good part about using different runners to run tests is that you often find niche cases that you would have otherwise missed. I was able to duplicate the behavior using msTest from the command line on the development machine. Then I noticed that when msTest runs it creates a whole new directory for each run ( based on timestamp ) in order to run the tests in isolation. I started to realize my problem as the files needed for the test need to be copied to the new directory. As I was using reflection to load some of the dlls msTest would have no instructions that I needed those dlls to be copied over as well.
The trick is to declare the needed dlls as deployment items for your UnitTests test class and you are in business. In my case I needed these three dlls.