Kobiton vs. Micro Focus Business Process Testing (discontinued)

When it comes to doing or performing testing on the applications or devices then Kobiton is the best option to go forward with. Kobiton is best for both manual and automation testing. It also comes with great features like appium scripts generation which really useful and less time-consuming and makes it really good to go with.

Incentivized

You may want to consider this solution if you are already using HP ALM and HP UFT. It's a nice add on and encourages the team to think more on building small component based tests and promote lot of reuse. Also, if your team want business analysts or any non technical people build tests based on the flows, its probably the best solution available now. On the down side, the execution times if you have too many components are not great and on top of that you have to pay extra for the licensing. You can also build such frameworks using more open source solutions like bdd solutions.

Incentivized

• Biggest advantage is - you can use the same components created for manual as well as automated testing
• It has a nice little feature called extended capabilities where you can easily automate tests SAP and oracle type architectures.
• Easy access library lets you create highly reusable and shareable components and the integrations is not that difficult

Incentivized

• If you are using components for automation testing, the time it takes to load a new component is too high and it sucks off the benefit of component based testing.
• You want to have many components in a test and so a BA can also create automated tests easily but too many components takes too long to executed .
• It comes with a cost. You can simply build a modular framework even without this framework and probably more efficiently.

Incentivized

The idea for building a component based modular test framework is great and it would be great add-on to HP tools if the add-on efficiency is made high and the cost is low.

Incentivized

• As the tool itself promotes re usability, we were able to cut down development and maintenance costs by good %.
• More than cost savings, out no technical folks started building automated tests based on user flows very easily.

Incentivized