BIQuality Discussions Rss Feed

New Post: WITH clause causing tests to fail

pavanbarnala — Mon, 07 Jan 2013 11:54:10 GMT

Yes, looks like only expressions starting with SELECT are allowed. Thomas, any update on this?

New Post: MSTest

pavanbarnala — Mon, 07 Jan 2013 11:44:23 GMT

Thanks Thomas. I managed to automate Nunit test execution using MsBuild. Works like a charm.

New Post: MSTest

tstrehlo — Thu, 18 Oct 2012 19:05:16 GMT

Hi Pavan,

thank your for the flowers. Regarding to your question have you seen the chapter 5 of the documentation? There you can find informations for the MSBuild installation, unsefull tools and a sample script.

Thomas

New Post: MSTest

pavanbarnala — Thu, 18 Oct 2012 15:34:11 GMT

Hi Thomas,

Your tool is cool. I used it in my project and it is good as a stand alone testing platform with Nunit. My next logical step would be to automate the test case executions from MSBuild. I couldn't find much useful information anywhere in this regard. Could you please give me some pointers on that?

Thanks in anticipation.

Pavan

New Post: WITH clause causing tests to fail

RodneyNolandBPE — Thu, 16 Feb 2012 21:32:25 GMT

Hi.

I haven't seen this anywhere, but creating BI.QUALITY test queries that include subqueries using the WITH clause fail, even though the same queries can be executed in MS SQL Management Studio without error. When I run these queries inside N-Unit I get:

BI.Quality.QueryTest.3-General\5-StaffDimension\DimStaffADPIDoverlappingDates:Exception ouccured while executing the query: Deferred prepare could not be completed.Statement(s) could not be prepared.Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.

I cannot terminate the preceding statement with a semicolon because there is no preceding statement. the WITH clause is effectively the first statement in the query.

Any help would be appreciated.

Rodney Noland

QA Developer

New Post: How to test Stored Procedures with this solution? any sample case?

scornik — Fri, 23 Dec 2011 08:27:42 GMT

Hi,

I am having difficulty to test stored procedures with this solution. Can you give some good examples to conduct unit test of stored procedures with this solution?

Thanks in advance

Ashik(scornik)

New Post: MSTest

tstrehlo — Tue, 01 Mar 2011 21:44:33 GMT

Hi,

as we designed the tool it was a main goal to create a unit test without compiling code. Therfore we use a testcase parameter mechanism which is offered by NUnit. All testcases you definie within BI.Quality are parameters for on testcase. We are Microsoft Gold Partner (and fans of Microsoft) but we havn't found anything compareable within the unit test architecture of Microsoft. So BI.Quality works currently only with NUnit.

Thomas Strehlow

New Post: MSTest

Angel_Roche — Tue, 01 Mar 2011 17:20:20 GMT

Hi,

in my company we are working with Visual Studio 2010 and MSTest instead of NUnit.

Does this tool can be used with MSTest? Is this planned in a future that can work with MSTest?

Thanks!

New Post: MDX query not working: "Object reference not set to an instance of an object."

BertusHolscher — Fri, 14 Jan 2011 14:35:03 GMT

Hi Adrian,

you are absolutely right. I tried the simplest MDX I could think of, but it turns out that it is too simple.

Thanks, it is working fine now!

Bertus

New Post: MDX query not working: "Object reference not set to an instance of an object."

apolko — Tue, 11 Jan 2011 18:19:54 GMT

Hi,

the issue you described above could be reconstructed on the AdventureWorks database. To workaround that issue you should select the default measure on the 0-axis.

Best regards,
Adrian

New Post: MDX query not working: "Object reference not set to an instance of an object."

BertusHolscher — Tue, 11 Jan 2011 08:51:17 GMT

I am trying to get ORAYLIS BI.Quality to work. SQL queries work fine, but MDX gives the following error:

SELECT FROM [Dekking] CELL PROPERTIES VALUE;

Message:

Object reference not set to an instance of an object.

I can run the MDX statement in SQL Server Management Studio without a problem.

This is the connectionstring

<Connection>
<Name>APM_APK MDX</Name>
<ConnectionString>
Provider=MSOLAP;
Data Source=RDWXXXXXX;
Integrated Security=SSPI;
Connect Timeout=5;
Initial Catalog=XXX;
</ConnectionString>
</Connection>

ValidateConnections works okay.

This is my testcase:

New Post: Oracle connection via OLEDB

apolko — Thu, 04 Nov 2010 08:41:42 GMT

Hi Mike,

thanks for the encouraging words to BI.Quality. If you like the product, we would appreciate a positive rating.
Coming back to your question: BI.Quality supports any Microsoft OLEDB provider. Of course we have not tested all of them.
The documentation is sketchy in some sections, but we are working on that.

Best regards,
Adrian

New Post: Oracle connection via OLEDB

MikeHoney — Thu, 04 Nov 2010 04:12:22 GMT

Hi Oraylis,

First up - thanks very much for putting this project up - it really fills a need. I got through the setup and created my first test project in just a few minutes (despite not being very familiar with NUnit), so you have done a great job.

My question is about defining an Oracle connection. I have been able to successfully define one and run a test, so it seems as simple as plugging the right OLEDB connection string in to the Connections definition?

Am I missing something or is that it? And by extension, does that mean you could configure Query tests for any OLEDB source (i.e. not just SQL Server or Analysis Services)?

If that's the case, it could be worth mentioning in the Codeplex project description and doco, as it would greatly increase the possible scope of your app.

Thanks again!

Mike

New Post: Column 'actualValue' does not allow nulls

apolko — Mon, 25 Oct 2010 08:04:32 GMT

Hi,

we are happy to announce that the new version of BI.Quality has just been released. The null value problem discribed in this threat has been fixed in the new release.

Best regards,

Adrian

New Post: Column 'actualValue' does not allow nulls

apolko — Tue, 12 Oct 2010 13:54:58 GMT

Hi,

we are working on a new release of BI.Quality, which solves the null-value issue. The new version is expected to be online next week.

Best regards,
Adrian

New Post: Column 'actualValue' does not allow nulls

MartinIhrke — Mon, 11 Oct 2010 15:14:18 GMT

Hi folks,

same question here. this makes testing of large datasets quite impossible since it mostly has some null-values. i don't remember such behavior at prior version anyway, so can this constraint be switched off?

best regards, Martin

New Post: Column 'actualValue' does not allow nulls

dmuller — Mon, 20 Sep 2010 09:47:02 GMT

Hello Oraylis !

Thank you for the rand new Release 2.0.0.

I have a question concerning a point that is not related specifically to the new release.

For some queries there might be NUll values. However this does not seem to be allowed for the actual result table.

"BI.Quality.QueryTest.NominatedExportByBRP:
System.Data.NoNullAllowedException : Column 'actualValue' does not allow nulls."

Is there a possibility to switch this constraint off ?

Thank you in advance.

Daniel

New Post: Test compatibility between 1.0 and 1.97

dmuller — Mon, 13 Sep 2010 12:02:53 GMT

Hello,

thank you for YOUR quick action. Please excuse my response being late.

Anyway, the day following 1.98 release, I installed tested and constated: Query Test passed, Test description passed not with the rsult file pattern.

As this is the beginning of our tests and your (new) pattern with XML and CSVFileWriter comes in pretty handy I changed the test description for all I my tests in order to go on with BI.Quality FW.

Thank you and keep going.

Daniel

On Wed, Sep 1, 2010 at 11:15 AM, apolko <notifications@codeplex.com> wrote:

From: apolko

Hello Daniel,

Thank you for your post. Actually there is a compatibility issue between version 1.0.0 and 1.9.7.
We are currently working on solving this problem and plan to release a patch version as soon as possible.
As a workaround (and in general) we recommend to transform your query test definitions into the new syntax (see documentation).
Your example definition should be redefined as:

<QueryTest>
<Name>ATerifficQueryTestName</Name>
<Description>Test Cube Name with white spaces</Description>
<XmlTableReader table="refTable" file="REFERENCE_AnOLDTerifficQueryTest.rslt" />
<Query
table="ATerifficQuery"
connectionref="MDX-OfTheThing"
include="ATerifficQuery.mdx" />
<AssertTable expectedtableref="refTable" actualtableref="ATerifficQuery" />
<XmlTableWriter tablered="ATerifficQuery" file="ATerifficQueryTest.rslt" />
</QueryTest>

Best regards
Adrian

Read the full discussion online.

To add a post to this discussion, reply to this email (BIQuality@discussions.codeplex.com)

To start a new discussion for this project, email BIQuality@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

New Post: Test compatibility between 1.0 and 1.97

apolko — Wed, 01 Sep 2010 09:15:45 GMT

Hello Daniel,

Thank you for your post. Actually there is a compatibility issue between version 1.0.0 and 1.9.7.
We are currently working on solving this problem and plan to release a patch version as soon as possible.
As a workaround (and in general) we recommend to transform your query test definitions into the new syntax (see documentation).
Your example definition should be redefined as:

<QueryTest>
<Name>ATerifficQueryTestName</Name>
<Description>Test Cube Name with white spaces</Description>
<XmlTableReader table="refTable" file="REFERENCE_AnOLDTerifficQueryTest.rslt" />
<Query
table="ATerifficQuery"
connectionref="MDX-OfTheThing"
include="ATerifficQuery.mdx" />
<AssertTable expectedtableref="refTable" actualtableref="ATerifficQuery" />
<XmlTableWriter tablered="ATerifficQuery" file="ATerifficQueryTest.rslt" />
</QueryTest>

Best regards
Adrian

New Post: Test compatibility between 1.0 and 1.97

dmuller — Tue, 31 Aug 2010 13:56:38 GMT

Hello,

thank you for the excellent idea and the promissing first implementation of Oraylis BI.Quality.

UnfortunateIy, I encountered problems when reusing the tests created with the first version with the actual one. Evidently, I noticed the changed schema but still cannot imagine recreate the test suite with any framework release.

The methode used was: Record a result file, use it as the reference in the comparing assert table test. I give an exemple xml hereunder.

<QueryTest>
<Name>ATerifficQueryTestName</Name>
<Description>Test Cube Name with white spaces</Description>
<ConnectionRef>MDX-OfTheThing</ConnectionRef>
<Query include="ATerifficQuery.mdx"/>
<RsltFile>ATerifficQueryTest.rslt</RsltFile>
<AssertTable include="REFERENCE_AnOLDTerifficQueryTest.rslt" />
</QueryTest>

This is not valid anymore for the actual version. It was however easily human readable.

Do I have to recreate the REFERENCE results by using XmlTableWriter/CsvTableWriter or can I reuse my recorded result files ?

Can you recommend another specific solution?

Thank you in advance.

Daniel