The testing of business object reports or in general any report is discussed below:
The following testing is required for business object reports
1) Data validation: this is to test if the report displays the data that is required of it. The data is formatted properly with cross tabs, blocks, sections, filters, etc.
2) The format of the report is correct i.e. the orientation, font size, page size, page orientation.
3) Check the print settings. Print the report to check if it prints property. Check if the report can be saved as excel/html/pdf format.
4) Regression test by comparing to older version of the report.
How to test the reports:
1) Scope definition: Testing scope varies depending on the changes involves i.e. if it is a new report or updates to existing report.
2) Regression testing: If is updates to existing report then refresh the older version of the report to compare that the changes have not impacted the existing report.Microsoft excel or beyondcompare are some of the tools that are used to compare two reports and check for any discrepencies.
4) Data validation: SQLs and eye ball testing can be used to validate the report data. Take sample of data and test it against operational/data warehouse data to check the data is accurate.
5) Universe testing: If testing scope involves testing the universe, then all the objects and classes that are required as per BRD can be checked to check they exist. Also, existence of any loops and any universe validation issues can be checked and resolved.
6) Implementation testing: After implementation, the report can be refreshed in UAT/prod environment to check if it is still working and displaying data. Check if the report is getting refreshed as per schedule and the report is getting published/emailed as per requirements.
See Also: http://dwbitechguru.blogspot.ca/2014/07/etl-testing-challenges.html
The following testing is required for business object reports
1) Data validation: this is to test if the report displays the data that is required of it. The data is formatted properly with cross tabs, blocks, sections, filters, etc.
2) The format of the report is correct i.e. the orientation, font size, page size, page orientation.
3) Check the print settings. Print the report to check if it prints property. Check if the report can be saved as excel/html/pdf format.
4) Regression test by comparing to older version of the report.
How to test the reports:
1) Scope definition: Testing scope varies depending on the changes involves i.e. if it is a new report or updates to existing report.
2) Regression testing: If is updates to existing report then refresh the older version of the report to compare that the changes have not impacted the existing report.Microsoft excel or beyondcompare are some of the tools that are used to compare two reports and check for any discrepencies.
4) Data validation: SQLs and eye ball testing can be used to validate the report data. Take sample of data and test it against operational/data warehouse data to check the data is accurate.
5) Universe testing: If testing scope involves testing the universe, then all the objects and classes that are required as per BRD can be checked to check they exist. Also, existence of any loops and any universe validation issues can be checked and resolved.
6) Implementation testing: After implementation, the report can be refreshed in UAT/prod environment to check if it is still working and displaying data. Check if the report is getting refreshed as per schedule and the report is getting published/emailed as per requirements.
See Also: http://dwbitechguru.blogspot.ca/2014/07/etl-testing-challenges.html
No comments:
Post a Comment