Skip to content
NBi is a testing framework (add-on to NUnit) for Business Intelligence and Data Access. 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# or Java code to specify your tests! Either, you don't need Visual Studio or Eclipse to compile y…
C# Other
  1. C# 99.2%
  2. Other 0.8%
Branch: develop
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.packages Add the explicit references to files in lib and tools Jan 3, 2020
Documentation Fix issue #236 about link to documentation Feb 7, 2017
Licenses Rename folder license into licenses to avoid issue with LICENSE file Oct 18, 2016
NBi.Core Merge branch 'develop' of https://github.com/Seddryck/NBi into develop Mar 17, 2020
NBi.Extensibility Fix tiny typo Sep 14, 2019
NBi.Framework Fix issue when the error messages are rendered in Markdown with an Al… Oct 8, 2019
NBi.NUnit.Runtime Implementation of custom-scalar and applicable to variable Nov 4, 2019
NBi.NUnit Implementation of merge for cartesian-product of two result-sets Mar 17, 2020
NBi.Services Extract content from project NBi.service to redispatch between UI and… Jul 16, 2019
NBi.Testing.Core Merge branch 'develop' of https://github.com/Seddryck/NBi into develop Mar 17, 2020
NBi.Testing.Framework Fix System.ValueTuple having different versions, update Moq and add d… Jan 6, 2020
NBi.Testing.GenbiL Add parser for the load optional Feb 3, 2020
NBi.Testing.Xml Implementation of merge for cartesian-product of two result-sets Mar 17, 2020
NBi.Testing Merge branch 'develop' of https://github.com/Seddryck/NBi into develop Mar 17, 2020
NBi.UI.Genbi Remap to the new package for StringTemplate Jan 3, 2020
NBi.Xml Implementation of merge for cartesian-product of two result-sets Mar 17, 2020
NBi.Xsd.Preprocess Update to last version of dependencies and prepare NBi.Testing for a … Sep 7, 2019
NBi.genbiL Add parser for the load optional Feb 3, 2020
librairies Add the binaries for some dll Sep 4, 2018
.gitignore Temp fix Sep 4, 2018
AssemblyInfo.cs Extract Tests for genbiL and Framework to new projects Jul 15, 2019
AssemblyInfoPatcher.ps1 Update references to the newly created PocketCsvReader library Jan 8, 2019
GitVersion.yml Some reviews around ScalarHelper and TestVariable Dec 23, 2018
LICENSE Update LICENSE Oct 7, 2016
NBi.sln Implementation of custom-scalar and applicable to variable Nov 4, 2019
Readme.md Update Readme.md Jan 3, 2020
Release.md Add new notion of duration for scalar values. Only exposed for sequen… Dec 23, 2018
UpgradeLog.htm Fix test failing in Nbi.Testing and move Core tests to another project Jul 15, 2019
appveyor.yml Reactivate all tests and change to only upload to GPR when beta or RC… Oct 9, 2019
azure-pipelines.yml Fix build configs Jul 15, 2019
clone-extensions.cmd Add a CMD to clone the extensions Mar 18, 2017
contributing.md Update contributing.md Apr 15, 2016
logo-2x.png Change iconUrl by icon in nuspec files Nov 1, 2019

Readme.md

Logo

NBi

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.

Social media: website twitter badge

Releases: nuget GitHub Release Date licence badge

Latest RC and beta: Pre-release GitHub (Pre-)Release Date nuget

Dev. activity: GitHub last commit Still maintained GitHub commits since tagged version GitHub commits on v2.0 GitHub commit activity

Continuous integration builds: Build status Build Status Tests

Status: stars badge Bugs badge Features badge Top language

Releases

Binaries for the different releases are hosted on www.nbi.io or GitHub

Documentation

The documentation is available on-line and is hosted on www.nbi.io

Licenses

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

A continuous integration service is available on AppVeyor and another on Azure DevOps

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

NBi is using Git as DCVS and the code is hosted on Github. Organization of the Git repository is based on Git-flow.

If you want to develop a new feature, you're encouraged to read the contribution guidelines.

NBi is mostly developed in C# with a bit of SQL and XML.

Tracking

This OSS project is tracked by Ohloh

Project Stats

You can’t perform that action at this time.