SAP Webi Dashboard Testing Best Practices
These testing techniques are not just for SAP Webi Dashboards of course. They apply to software testing in general and have been tried and tested across hundreds of development projects.
- If there are 2 bugs, report 2 bugs separately. Don't submit 2 bugs together.
- If there are 2 requirements, then write 2 separate and independent requirement documents. Don’t mix two on one document.
- When defining requirements, start with a coarse definition level, then through multiple passes using progressive iteration, define the details as you know and discover them.
- Give each item a unique sequential number.
- The reason for both is tracking and management of both is easier.
- You might be able to close 1 quickly but the other one may remain open for months. The end result is, both appear to be open for months.
- By tracking each item separately, you can close the closed or finished ones and move on.
Otherwise, you can never move on.
The time saved by mixing topics winds up costing more time down the road. - Seems like a no brainer, but you would be surprised how many people try to "save time" or "save effort" by mixing topics.
- I've tried it myself, but I had to learn the hard way, what the easiest way to track items was.
Do it separately. - Do not multi-task. Trying to split your time 20%-80% or 50%-50% does not work and is just stupid.
Focus 100% on each issue until completion then move on to the next issue. Otherwise, you will have many open items that are unfinished and you can never move on.
As you can see, testing is something you have to set up for success from the start. We've also prepared an additional checklist you should get and follow to ensure your SAP Testing efforts are effective.
Got some other techniques you want share? Let us know!
More reading:
Take a Deeper Dive into Aircraft Cockpits Vs Dashboards
