Skip to content

v1.10-beta

Pre-release
Pre-release
Compare
Choose a tag to compare
@Seddryck Seddryck released this 13 Jul 22:18
· 1582 commits to master since this release
v.1.10.0.10
0173fd6

Release 1.10

This release 1.10 introduces a few new features and fixes a list of bugs. But the more important change of this version is, probably, that we've moved from Codeplex to Github. It's also the opportunityto reveal our new website and url at www.nbi.io This move is important because the documentation needed to be partially rewritten and the software management system has been changed from Mercurial to Git ... more details here under.

This release and the next will be downloadable from there.

What's new ?

New features

  • Support the testing of structure for relational database: you can use the assertions exists, contain, equivalent and subsetOf on objects from a relational model including table, views, schemas (More to come in next releases). More info
  • Support the testing of sets for the structure of tabular and multidimensional models. More info
  • Support the testing of members of sets for tabular and multidimensional models. More info
  • Support of a default type (text, numeric, boolean, dateTime) for columns identified as value. More info
  • Support of keys with a different type (text, numeric, boolean, dateTime) than text. More info
  • Tolerance is now supporting a combination of a percentage and a minimal/maximal absolute value. More info
  • Improved performances when loading a test-suite with NUnit GUI.
  • Improved user-experience when creating a test-suite with ETL. If some attributes are missing in the definition of the etl, NBi will clearly report the missing attributes.
  • Additional partial xsd are also available for the xml elements test, settings, setup and cleanup. See in folder framework, sub-folder schema.

Bug fixes

Framework

genbi

Major refactoring

  • The code supporting the assertions of structure (model) has been refactored to improve maintainability and speed up future development.

Move to github

Why do we leave Codeplex

In a few words: no new feature and no bug fix. To illustrate this, the tab "Source Code" is suffering from a bug since more than six months. Github is really further than codeplex and the gap between the two tools is growing everyday.

Consequences of this move

What's next ?

Main ideas for release 1.11 (or next)

  • Create fakes or stubs of views, stored procedures or functions during the setup of a test and remove them during the cleanup. Work already started
  • Support tests on the xml of a report (SSRS). Work already started
  • Support assertions about the count of rows added (or updated or deleted) in a table after the execution of a SQL statement or a ETL.

Other ideas probably not for 1.11 but for later

  • Support to surround the test with a transaction and rollback the transaction when the test has been executed.
  • Execute tests with etls running on a remote server.
  • Add a setup command to process parts of a cube (SSAS).
  • Support some tests about result-sets, to express easily conditions such has "If this field is greater than X then this other field must be greater than Y".
  • Support transformation of the result-set in the assert (move columns, remove columns, add columns).

I'm (still) working on a Release 2.0. This work is delayed to the lack of GUI for NUnit 3.0. 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

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.

Assets 3
Loading