We are interested in acquiring a Katalon license for a team of 10-15 people, and we have a few questions to ensure the tool meets our needs. Could you please provide detailed information on the following:
License Options:
What are the license options available for a team of our size?
Are training and support services included with the license?
Keyword Usage:
Does Katalon allow customization of existing keywords or the addition of new ones?
What tools are provided for managing and organizing keywords?
Debugging Features:
Does Katalon offer step-by-step execution or variable tracking during debugging?
How are logs and reports managed during the debugging process?
Reporting and Re-Execution:
After running a test suite, how are detailed reports generated?
Is there an option to extract error-prone areas and re-run only those parts? How does this feature work?
GitLab Integration:
What integration features does Katalon provide for GitLab?
What are the steps and configurations required to integrate our project into the CI/CD pipeline?
Performance Testing:
What tools and features does Katalon offer for performance testing?
Are there any limitations or issues we should be aware of when using Katalon for performance tests?
Cache Usage:
Is there a feature to use cache for sharing data between test suites?
How can we create a single subscription and use it across all test suites?
Thank you for your assistance!
Katalon offers no products designed for performance testing. You should look other products, such as JMeter.
I don’t see what you mean by “data” here. You should make it clearer.
Is it a “username/password” pairs? Is it a DB query result sets fetched by your test scripts? Is it Request-Response messages exchanged between browser and web servers? Is it a set of PDF/Excel files downloaded from web sites? Is it a bulk of screenshots of browser window? Is it a log of test execution? These are quite different in nature. You should not mix these stuff and call it by one word “data”.
I don’t know any built-in feature that Katlaon provides as “cache for sharing data”.
Of couse, you can create/read any local file(s) by programming Groovy scripts. If your test writes data into local file(s), later, any test suites would be able to read the files. Isn’t it enough? You can read/write files on a remote file server as well.
I used my imagination a lot to guess what you want.
I thought you might be interested in a library named materialstore that I developed for my own sake. See the following post, which suggests a bit about the functionality of the materialstore.
Backed by the materialstore libary, my test suites can process (save/retrieve/compare) any type of files (PDF, Excel, HTML) collected during UI test runs. My test can compare (make diff of) the files collected today with the files collected yesterday, and ones collected last week.
My “materialstore” has no dependency on Katalon products.
Is there a feature to use cache for sharing data between test suites?
How can we create a single subscription and use it across all test suites?
Thank you for your assistance!
I guess this means that you want the ability to have dependencies between test cases?
Eg test case 1 creates a new ‘subscription’ (whatever that is) that might have a username and password for example? If so, this can be achieved by storing as a global variable, whereupon test case 2 executes next and uses the newly-created username and password. Or you could write to a text file or a spreadsheet, if something a bit more permanent is required.
