Testing in qlikview

[deepakqlikview_123]

Hi All,

I know about unit testing in QV that is matching dashboard level value with database value.

Can you please suggest different ways in that way we can test QV application successfully at our end.

Thanks in advance.

thanks,

Deepak

[tresesco]

There is no such ready made recommended ways to test and validate your qv reports. You have to just compare source data and qv generated reports upto some extend. Like run similar SQL command in source data and verify results.

[sujeetsingh]

Deepak,

testing include checking from backend and the report

values for the filter selection

performance testing

.. A lot more

Follow this

http://community.qlik.com/docs/DOC-5901

[avinashelite]

Hi Deepak,

*Always verify the data and its count by querying the data base and check the consistence with the QV dashboard.

*Check the filters working properly by verifying the data and associated data with it.

*Always try to eliminate junk value which may occur due to wrong data modeling.

*Check the performance of the QV based on different size of data load

[jagan]

Hi Deepak,

There is no readymade tools to test the QV Dashboard, you have to valid your data against the Datasource (May be database or flat files.)

Regards,

Jagan.

[deepakqlikview_123]

Hi All,

Thanks for your prompt responses many things are clear for me now.

I have only one doubt if there is no tool for testing Qv application then in big projects how to test QV application .

I mean is there any automation tool  available in mkt which can helps in those activity.

Moreover please suggest what would be responsibility for testing team.

Thanks,

[#7 · Accepted solution]

Hi Deepak,

Have you completed your testing?

I am also on the hunt for some framework that would make testing a more natural part of QlikView development. So far I find that SQL best practices for testing are more applicable to QlikView than other software testing, so that might be a good area to search for ideas for testing your script.

Also a good idea is to create a test database so that you have a controlled input to your application which makes it easy to know what KPI values should be etc., Also you can try invalid inputs with nulls or forbidden characters to see if your application can handle it.

Lastly, if you want to check your application performance by loading from a large self generated test database make sure that you have unique values in fields where you would expect the real database to have unique values. That is remember during testing that unique values makes an application more resource consuming than fields with repetitive values.

[deepakqlikview_123]

Thanks Jonaz