seddryck / nbi Goto Github PK

It'd be a good idea to add facilities to create a transaction around a test and to rollback it after the test's execution.

It will be useful to be able to fake and/or stub stored procedures or functions to test some parts of your BI solution.

Stub: temporary replace SP/function by a fix result set
Fake: temporary replace SP/function by another T-SQL code.

It's really powerful to be able to test against the dataset, but sometimes there are business logic in the report elements. So maybe it could be possible to test against the atom-feed of the report? I am pretty sure its no trivial task, but it could be a cool feature.

Daanoj

Hi Seddrick,

When I add the option timeOut_MilliSeconds="value" in a test script, NUnit doesn't load the testsuit and gives an error. The error is: The test suite is not valid. Check with the XSD.

Examples:

This works:

<fasterThan max-time-milliSeconds="2000"/> 

This doesn't work:

<fasterThan timeout-milliseconds="1000"/> 
or 
<fasterThan max-time-milliSeconds="2000" timeout-milliseconds="1000"/> 

Greetings Daan

Jenni_P:

Hi,

I'm using NUnit / NBI in my project.
But i have a important volumetry issue.

I compare two queries, aroung 800 000 rows.

But i have this message :
NBi.NUnit.Runtime.TestSuite.Compare CodeActe,count(*) on CubeDimActe+CubeDimActe2 :
NBi.NUnit.Runtime.CustomStackTraceErrorException : The expected data set has some duplicated keys. Check your keys definition or the result set defined in your assertion.

Using the query in my database, i have already checked the result. It's seem ok. No duplicated keys.

Does a row number limitation exist ? How i can solve my issue and continue using this software ?

Thank you,
J.

If you are using a 12-hours format, GenBI generates an invalid XML and all tests fails.
I'm now using EN-US 12-Hours time format and this is what is generated by GenBI:

which is not a valid datetime.

The correct value is

GenBI should always generate datetime formats following the ISO 8601

YYYYMMDDTHHmmSS