I used to work with Selenium at the start of my career, but right now, from the last almost four and a half years, I'm working on Leapwork automation tool.
For automation, I used to work on different tools such as JMeter and Selenium, but when I joined Tyler Technologies, USA, we were trained for using Leapwork, and when I use it, I simply love Leapwork. As far as the other tools, we use other tools for management purposes, such as TestRail, Jira, and other software. For automation purposes, we mainly work on Leapwork to automate our processes and scripts.
Basically, we follow the CI/CD testing environment, continuous integration, and continuous development. What we do is there is a product, ABC product, and we receive a request from a client to add a feature in this product. Before adding that feature, we have data and reports from the past that show the behavior of our product, the current bugs, and the number of test cases which got passed or failed. Then we integrate and add the feature which the client requested. After adding the feature, we simply run all test cases again, including the previous ones which we had before adding the feature. Then to test the new feature, we write new test cases, create automation flows, run them, and then run the whole regression run of flows to test the new feature.
TestRail is a tool where we have test cases for our ABC product. Test cases mean there is one module in the product, for example, the payment module. To test that module and verify if it is working properly, we write steps. We use TestRail to write these steps. In TestRail, we have options in which we can write the step-by-step process of each test. We can write one single test in multiple steps to make it more understandable.
TestRail has many great features. We can use attachments with it, such as videos or screenshots for proof or for any new user who is not familiar with the product. The steps can be edited by anyone and we can see the history as well, including who has edited or modified the test steps. The reporting capabilities and the simplicity of it make it user-friendly, as new users can easily understand the tool. The simplicity would be the greatest benefit of TestRail.
I have integrated TestRail, Leapwork, and Jira together using PowerShell scripting. When we have 100 test cases and before every release goes out to our customers, we kick off the regression run in Leapwork. At runtime, when the test case passes, it reflects the results on TestRail. If it fails, it automatically creates a Jira story and sends that story to our backlog for further investigation to determine if it's a product issue, Leapwork tool issue, or a logic issue in the automation scripting.
