The release 1.5 includes new features about test execution management (setup, cleanup, ...), query's extraction from SSRS report and a new way to check a result-set based on evaluation of expressions within a row. This releases includes also several fixes about usage of parameters and template-variables in queries previously shipped with version 1.4.1 or newly fixed in 1.5.
Please report all the bugs to the issues tracker to ensure they are fixed ... even if they are minor issues.
What's new ?
- Setup and Cleanup to execute actions before and after the test.
- Conditions to specify if the environment of a test is adequate or not to run a test and if not ignore it.
- A new way of validating result-sets based on definition of expressions (more info here)
- The possibility to extract a query from a report and use it to validate performances, syntax or result-sets
- A new scope for default named everywhere to pass parameters or template-variables to assertions and system-under-tests.
- Fix #21 about special chars in an xml element parameter . Now, these special chars are not taken into account when reading the value of the parameter.
Previously fixed in 1.4.1:
A Blog named Ambiguity vs Information
about Business Intelligence is writing some posts about NBi and how to test your BI solution with it.
What's next ?
This release is the first one touching a new component of the Microsoft BI suite with SSRS. The next release 1.6, will go further and will also include SSIS. We plan to support the execution of an SSIS package and an SSRS report (in a setup or as a system-under-test) and validate the time needed to execute it, the success (or failure) of this execution or the state of the content of a table after the execution of the package.
I've also received by e-mail a few feature requests and will try to implement them. But some of them are related to the next point.
I'm working on a Release 2.0. This work is delayed to the lack of releases for NUnit 3.0 (and changes in the API). Anyway the goals are still:
- Lot of internal refactoring meaning easier to integrate new features (mostly done)
- Compatible with NUnit 3.0 meaning easier to setup a test suite !
- Easier to port it to another test framework than NUnit (xUnit, Fixie, ...)
- Easier to write helpers to compare result-sets
- Easier to create a Visual Studio Add-in
Will also try to integrate FubuDocs to the project to manage documentation.
Naturally this Release 2.0 has a big constraint linked to the availability of NUnit 3.0 (currently still not available) so no planned date for the moment.