Quality is delighting customers
I am working on OBIEE reports testing.
The documents we have been provided with is the metrics and report description.
I am facing dificulty in visualizing those reports description as images(actual reports).
Is there anything else that should be provided for writting the tets cases for reports?
Any suggestion will be helpful.
I am not sure I understand the question, and I apologize if I am not answering what you are asking.
Reports can be challenging to test. In my experience, reports are the last part of a project that anyone pays attention to. There are frequently no requirements. If there are requirements, they are frequently not specific enough to translate into test cases; someone describes a general goal for the report, a developer translates that goal into a report, and then they iterate until all parties are satisfied. It is difficult to translate a loosely stated goal into a set of rigorous test cases.
If the goal isn't specific enough, sometimes you can ask the developer to help you understand the requirements in enough detail to write test cases. The requirements might be a natural language description or they might be a set of SQL queries.
Another option is to ask for a set of sample inputs and corresponding sample reports.
If you start with SQL queries, now you have two problems. First problem: you need to verify that the report does what the developer intended for it to do, i.e. you need to write test cases that verify what you think the queries are intended to do. Of course, even if the SQL queries work perfectly, they still may not produce the report that the original requirements (or the original goal) described. That brings you to the second problem: you need to decide whether the developer understood the report's original goal.
Another way to approach the report testing is to give up on understanding the report's goal, and instead to focus on regression testing. For example, if you are working with an existing report, and now the report needs to be re-tested because the underlying schema has changed, you may want to *assume* the original report was correct and instead focus on whether the report still produces the same output if you begin with the same input.
I hope that helps.