P. 1
Report Testing

Report Testing

|Views: 25|Likes:

More info:

Published by: Optimus Information Inc on Aug 28, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

12/11/2015

pdf

text

original

Report Testing

Challenge:
Our client had an existing vendor develop reports about supplier surveillance, supplier approval, etc, using the BRIT reporting platform. The client was now looking for someone to help test the functionality and data of these reports. Our client’s key need was validating the data within their existing reports. As well as they wanted to conduct overall tests of the reports, which would look at report location, report parameters, fields, layout, and the complete UI. Key challenges: 1. There was a complex data base structure that consisted of hundreds of suppliers and over a million manufactured pieces. 2. The business process was not captured in any document, therefore we needed to exert significant effort in learning about the domain. 3. There was complex business logic for each report requirement. 4. Most reports were multiple level drilldown reports.

The Client:
The client is a company that specializes in providing software solutions, which help the aviation industry improve their operations.

How Optimus Helped:
Optimus’ team had an orientation session with our client’s operations manager to understand their different business modules and processes. We then developed a plan for testing the report and shared it with our client. All the terms were agreed to before the project commenced. Optimus met the vendor’s QA and development lead to understand what the high level project requirements were. Throughout the project, we worked with the QA lead and consulted the tech lead for any database related questions. For data validation, we developed complex SQL scripts that were specific to each report’s requirement. We compared the outputs from the SQL to the figures projected in the reports using relevant parameters. For report functional testing, our team used a requirements document that was specific to each report for reference. The test cases and results were reported in another document specific to each report. The defects were logged in JIRA, our client’s defect tracking system. Reports with a list of issues to work on were sent to our client’s developer. Since supplier surveillance and approval data can be quite sensitive and crucial for an airline company, the QA services provided by Optimus assured our client that they had quality business intelligence from their supplier data.

The Process:
1. Understand the client’s needs and orientation. 2. Understand the database and data structure. 3. Identify the report requirements and the scope for testing. 4. Build test cases and update results for each report, with the SQL scripts. 5. Log defects in the client’s defect tracking system.
Technologies used: SharePoint, Oracle SQL Developer, Integrated Supplier Information System (ISIS), Actuate BIRT, JIRA

About OptimusBI
OptimusBI, the independent BI practice of Optimus Information Inc, provides Business Intelligence services including data warehousing, reporting services, dashboarding, data management, and text analytics. Our services can be delivered on premise or via the cloud. Connect with us to see how we can be a seamless extension of your technology team. Optimus Information Inc. #120-1412 West 7th Ave, Vancouver, BC, V6H 1C1, Canada Phone: +1. 604.736.4600 Email: info@OptimusInfo.com Website: www.OptimusBI.com Connect with us on the following networks:

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->