NBi is a testing framework (add-on to NUnit) for Business Intelligence. It supports most of the relational databases (SQL server, MySQL, postgreSQL ...) and OLAP platforms (Analysis Services, Mondrian ...) but also ETL and reporting components (Microsoft technologies).
The main goal of this framework is to let users create tests with a declarative approach based on an Xml syntax. By the means of NBi, you don't need to develop C# code to specify your tests! Either, you don't need Visual Studio to compile your test suite. Just create an Xml file and let the framework interpret it and play your tests. The framework is designed as an add-on of NUnit but with the possibility to port it easily to other testing frameworks.
The documentation is available on-line and is hosted on www.nbi.io
NBi is available on the terms of Apache 2.0. NBi is also using several OSS projects as libraries. All these projects, and their respective licenses, are available in the folder "License".
Bugs, issues and requests for features
The list of bugs and feature's requests is hosted on GitHub
Continuous Integration and Testing
NBi has around 2750 automated tests, asserting most of the features supported by NBi during the build processes. These tests are organized in three folders:
- Acceptance: The tests are effectively written in nbits file and played end-to-end by the framework itself. They don't use any fake, mock or stub and are connected to real databases and cubes and perform queries on them.
- Integration: These tests are used to assert interactions with external resources such as databases or cubes. They make usage of stubs to define parameters impacting the code to use.
- Unit: These tests are never contacting an external resource and have a maximal scope equivalent to the code of a single class. Usage of stubs, fakes and mocks is welcome.
In order to be able to build the software on different machines, the database and cube used during tests must always be Adventure Works 2008R2. In order to facilitate the integration, NBi is connected by default to the online SQL database hosted on Azure (Unfortunately no equivalent for SSAS). If you want to override the connection settings to execut the tests on your own environment, create a file named ConnectionString.user.config in the folder NBi.Testing and copy the content from the file ConnectionString.config into it, before adjusting for your environment.
Note that all the tests are not executed on the continuous integration services, due to limitations in the availability of some components.
- Unit tests are always executed
- Integration tests are executed based on the availability of the underlying components:
- Database Engine: Yes. Due to the usage of an Azure database to run these tests, these tests are enabled on the CI platforms. About ODBC drivers, the ODBC driver for SQL Server (13.1) is used on appVeyor and the SQL Server (10.0) is used on Azure DevOps
- OLAP Engine: No
- ETL Engine (SSIS): No
- Windows Service: No (but planned to integrate them)
- Local Database: No (but planned to integrate them)
- Report Server: No (but planned to integrate them)
- Acceptance tests are partially run. The test-suites covering the acceptance tests are executed but will return an ignore result when at least one of the test is not runnable due to service not running (most of the time, the reason for an ignore is the unavailability of Analysis Services).
Three artefacts are packaged and published by this CI:
- Framework.zip contains the dll needed to run tests written with NBi
- UI.zip contains the exe and dlls needed to run Genbi
- Nuget packages
The nuget packages built on appVeyor are pushed to nuget for beta, release candidates and release branches.
Code and contributions
If you want to develop a new feature, you're encouraged to read the contribution guidelines.
This OSS project is tracked by Ohloh