Thanks Manpreet this is only discussion not information.
I am with you and it is really important for any business to earn profit and Katalon has to do so. I think this is right approach for KTS team but do not take away free tool and its capabilities.
@Vijay_Singh I think running CI/CD should be a free option not paid option. Currently RE is node locked which means if you have one 2 servers where you want to run test at same time then you need to pay for 2 RE licenses which will be very difficult to sell it to management. My understanding might be wrong but this is what I think. But I also understand Katalon team cannot keep building this product for free.
In my opinion, monetizing the RE is really a good middle ground for the Katalon dev/business team. I think everyone can agree that KS is a great tool, and that’s no accident: the dev’s have worked their tails off and have listened to community feedback better than most others in the industry. So of course, they deserve to be compensated for that.
Removal of the script/profile quotas was a good move for them. I think that was seen by many as a very clear pay wall, and one that most individual users could not justify paying for.
On the other hand, having the RE be paid software makes sense, because running from CI/CD is primarily a feature that enterprise-level users would utilize, and thus is fair game (IMO) to monetize over functionality that the average, individual user would care about.
Just my 2 cents.
in addition to what is already expressed … do not forget that maintaining valuable servers for serving implied services, e.g. the download, forum, analytics cost money.
so no matter how someone is willing to give a tool for free (even opensourced) to offer it without end-user frustration do cost. a lot.
dev/product owner frustration because lack of bandwith, need to scale, need more automated test on the build stage,handle the issues prioritise them …
should i mention also that somebody have to write the docs too? and keep it updated?
and skilled techwriters are even more difficult to find than skilled programers … just saying …
Katalon is undoubtedly a unique automation solution. Its e-co system (Studio, TestOps, etc…) provides team abilities to develop scripts faster and scale executions further, and that is nearly a development requirement nowadays to get the test results fast and reliable.
That being said, I can see why it’s being monetized to supplement the funds and motivations for Katalon developers behind the screen to continue delivering cool features/improvements to achieve automation goals efficiently. Testing is a huge ocean, once you go wrong it will sink you down no matter what, and the efforts to revert the sinks might not be acceptable in many teams.
Working with automation tests is a joy but also a pain without having the right solution. You are assigned to do automation for this website, this mobile application, or just this APIs collection and you’ve found an immediate tool to let you complete that quickly. That’s fine until one day you are not developing the test scripts alone, or the managers tell you to scale executions on cloud, or on different machines, or on contained Docker. You try to see again is my current tool support, if not then I have to develop it myself? What about the current test scripts? Should I migrate them too?
Over the time, this is the most exhausting brain leakage I’ve observed, and Katalon does provide a solution to adapt it all with the best among other solutions I’ve tried. I think they see it’s the time to let this model go live after many considerations and concerns.
We are a small company and very very new to test automation. I just had a few weeks this year to try to design some test cases.
I really can understand that KS-Team want and need to earn money to build such a very cool tool.
What my problem is how they did the transfer from freeware to a buying model. It wouldn’t be a problem for me if the old feature would last in the KS version and new features like desktop testing or other new cool stuff is only available in the KSE version.
But so, when you build up many test cases and suites and you use advanced KS-techniques now you have to change to the KSE version. For me I will continue using the KS 6.3.3 version so long it can be used and maybe in future we will change to KSE 7,8 or any other version of it.
To be honest, the documentation is often written by the community who usually provide better answers. There are better ways for monetizing software than blocking key-features with a overpriced monthly fee. (Think advertisements, donations, affiliates etc.)’
I personally find it a really sly way how the Katalon team is handling it.
I fully agree that removing some of the basic features to paid version was a bad move. We use debug a lot to help in writing and maintaining keywords to handle Dynamics CRM pages and flows. Now with debug a paid feature, this has caused management to review decision to allow us to use Katalon over their previously approved tool UFT, a tool that is so inflexible and super expensive.
Put it this way. If I was a group just starting out in looking at tools, and I get Katalon free to try it out by recording and then trying to play back tests and they fail, with no way to find out why except logs I would reject Katalon.
Now we have to review other tools to see what we should do moving forward. I lean towards Groovy+Geb+Spock now, since it will allow me to migrate my keywords.