March 13, 2013 at 3:31 am
Hi All,
I've been doing a bit of searching round for ways to unit test cubes and the results seem to be limited. What we're trying to do is make sure that any releases we make to live don't alter the existing numbers, unless we are aware that this should be the case, obviously we'd then make a change to the tests.
I've been toying with the idea of creating framework using ADOMD.NET, but this appears to be limited to single result set numbers, e.g.
Select [Measures].[Total Sales Value] On 0
From [My Cube]
Where [Date].[Year - Month - Day].[Date].&[20130313]
Does anyone have any ideas? In the meantime I'll continue searching round for ADOMD.NET stuff and post back any results I find.
Cheers,
Jim.
March 15, 2013 at 3:29 am
Hi All,
Just thought I'd drop a note back to say that I found some software on codeplex that can do this for you. It's called QueryUnit, which builds a dll that can be consumed by Nunit, which integrates directly with Visual Studio 2012.
So I've now set up about 30 tests for different measures and such like that executes against live to test that nothing unexpected has changed after releases.
Hope this helps someone!
June 13, 2013 at 4:23 am
Hi,
You should try NBi available at nbi.codeplex.com If you compare it to QueryUnit, it's easier to spot the difference between the expected resultset and the result of the test execution (especially with large resultset).
With NBi you can also test the structure of your cube and check that dimensions, hierarchies, measures are avilable. Other features include also the possibility to check your memebers in dimensions/hierrachies.
You can create large test-suite with this tool, on our side we've more than 2000 tests on the structure and the test-suite run without problems.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply