Integration testing with Azure development storage
Posted on January 12, 2012
I’ve been working on some classes that write data to Azure table storage. These classes of course need to be tested. Unfortunately the development fabric only spins up when you F5 an Azure project. This is a little problematic when the execution is from a unit test framework.
Some quick searching brought up this post which provides 99% of the answer. The only hiccup with this solution is that it is targeting the 1.0 version of the Azure SDK. I have updated this code to work with the 1.6 version of the SDK.
namespace MyProduct.Server.DataAccess.Azure.IntegrationTests
{
using System;
using System.Diagnostics;
using Microsoft.VisualStudio.TestTools.UnitTesting;
/// <summary>
/// The <see cref="Initialization"/>
/// class is used to run assembly initialization work for the test assembly.
/// </summary>
[TestClass]
public class Initialization
{
#region Setup/Teardown
/// <summary>
/// The assembly initialize.
/// </summary>
/// <param name="context">
/// The context.
/// </param>
[AssemblyInitialize]
public static void AssemblyInitialize(TestContext context)
{
StartAzureDevelopmentStorage();
}
#endregion
#region Static Helper Methods
/// <summary>
/// The start azure development storage.
/// </summary>
private static void StartAzureDevelopmentStorage()
{
Int32 count = Process.GetProcessesByName("DSService").Length;
if (count == 0)
{
ProcessStartInfo start = new ProcessStartInfo
{
Arguments = "/devstore:start",
FileName = @"C:\Program Files\Windows Azure Emulator\emulator\csrun.exe"
};
Process proc = new Process
{
StartInfo = start
};
proc.Start();
proc.WaitForExit();
}
}
#endregion
}
}
Dropping this class into the test assembly will ensure that the Azure development storage is running before the integration tests are executed.