The biggest advantage of Business Process Testing is that not only technical skilled people can participate with test automation but also business analysts, which will create better test cases then test automation experts can. The maintainability is also much better than in traditional approaches, but that also might depend on the architecture which is used.
Improvements to My Organization
Because everyone can create test cases, not only the quantity but also the quality is improved, which results in less defects in production. Also, there is less dependency on technical consultants so they can focus on other tasks.
Room for Improvement
The run speed is not as fast as if a local script would be running, but that is one of the downfalls of using a client/server approach.
Use of Solution
I started using it for about four years ago. Back then we used ALM 11 and BPT with QTP technology.
We have a DTAP environment, deploying in production takes a bit more effort than in a test one because of the security dependencies we have.
There are no stability issues.
Scalable is key for BPT as for one project we are using it with 50-100 users. When scaling up, it’s important to have a small team which is responsible for the framework while the rest of the team is just using it.
Customer Service and Technical Support
To be honest, technical support is not that great. We use CGI for technical consultancy who are a bit faster and better than the support of HP. The R&D part of HP is helping us with issues that they cannot solve.
Before using BPT, I mostly used TD/QC in combination with QTP. We used it with a custom framework. The main issue with most test automation frameworks (including the last one) is that they are highly technical and are hard to maintain. This resulted in a high dependency on third parties instead of being able to let the scrum team being able to be self sufficient.
Test automation specialists helped us with setting up the framework. It should be done with experts because the architecture has to be setup in a way that matches with the client.
The BPT framework is very flexible, which can result in suboptimal results when used by inexperienced users.
CGI helped with implementing and training the teams. We have three defined levels of test automation; level one is creating test cases, level two is modifying components, and level three is changing the framework components.
ROI is in most projects within a year if you compare it with manual testing. For smaller companies the HP tooling is indeed an expensive one.
ROI is not easy to calculate because there are some benefits which are not comparable with currency. For example, how do you rate quality.
It has room for improvement, but in my opinion it’s at the moment “best in class” when used in a (bus) DevOps environment. The most important part is that the components and flows should match with your product under test. Involve the business at the start of the implementation phase.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Feb 08 2016