ACCELQ vs TestRail: Which is a better fit?

Sandeep: I'm Sandeep, I'm currently working at a startup called Clarity, which is having 150 employees. And so I would rate ACCELQ as a five out of five. I used to work with the various traditional automation tools, which are license free, such as Selenium, or some of the JavaScript based automation tools. The reason they did not work for me is there are two key things. One is the effort involved in maintaining the setup. Usually if we consider Selenium or any automation tool where we have to set up everything from the scratch and we have to take care of the maintenance. And if there is a change, if we want to scale it up, so we have to take care of the maintenance as well at the framework level or the design level. And the second part is, I'm currently working on an application which is based out of Salesforce platform. Usually when we are working with Salesforce or any kind of CRM platforms, so we may encounter some UI challenges such as short adopts or any kind of those. These challenges, we manually have to deal with them. We have to customize our scripting and we have to deal with them. These are the two reasons I was looking for an advanced automation tool, which has the capability to resolve and also have the capability of having its own built-in framework and all. The reason we have chosen ACCELQ is the AI-based advanced capabilities that ACCELQ is having. I'll start with the design level aspects. Usually whatever the framework design we do before starting our scripting, so we don't have to deal with that. ACCELQ, you can use it as a web instance, and it has the inbuilt components or entities, whatever we need at the scenario level or at the object repository level, or test suit level. So everything is already taken care. All we have to do is start building the scripts. And also, when it comes to building a UI automation we have to deal with the object repositories, and also we have to take care of capturing the UI element properties, and then having them organized in our framework. ACCELQ will take care of all of them. It works based out of an image based mechanism, so all you have to do is capture an image and it will be able to identify. And in the recent version, ACCELQ has more additional capabilities. It doesn't even bother about the UA element properties. Based on the label, it will be able to identify the UA elements. So it is more advanced. We don't have to spend too much of time in maintaining the repository, we can focus more on the implementation part. And also, ACCELQ has more predefined methods such as whatever the UA action that you have or validation part that you need, all of them are already captured and wrapped in the package. So you just have to do is, in your plain English language you can search for the command and you can use it in your scripting. And also, the reporting is very advanced. In any of the traditional automation framework we have to build a reporting and we have to customize it as for our needs. ACCELQ has inbuilt reporting, which is more advanced, and we will be able to inject CI/CD capabilities as well, like scheduling the job or rerunning. Those kind of things as well, they're already incorporated within the ACCELQ. These are some of the capabilities which direct our attention towards it. One of the key advantage with the ACCELQ is, we don't need any prerequisite or previous knowledge on any automation. You can directly get started with ACCELQ because it is completely developed with the plain text. What the commands or even the overall design, it is very user-friendly. Even when we have a new QA engineer join our team, they don't need any previous scripting knowledge or automation expertise. They can directly get started with the tool because everything is very easy to understand and we can even relate it. That's how ACCELQ was built. When you are choosing an automation tool, or when you want to switch to a different automation tool from your traditional automation, you can get a POC instance. You can request for a POC instance, as ACCELQ does not provide any trial version. You can see if it is falling in your requirements and matching with your requirements. And also, the ACCELQ subscription model works in a different way, so you can compare it with our available automation tools and see if it is falling in your budget.

Berny R.: Hi, my name is Berny. I'm the head of QA. I give TestRail a five, and if you want to know more, click down below. We used to use SharePoint lists to do our test case management, and post that we actually implemented Zephyr for JIRA to manage our test cases, and it became quite clunky. We were really finding that creation of master regression tests for our projects was becoming quite time-consuming, and so at the end of each project we would take hours, if not days, to actually create a regression suite of tests, and so it was for that main reason that we decided to move to TestRail. We had four main reasons why we decided to choose TestRail. One was the ability to be able to easily copy and move our tests from a project suite into a master regression suite. One of the really important features for us is just around being able to navigate quite easily through the system, because we've got some business users who are quite new to test case and creating of test cases, so it needed to be user-friendly, which it was. We have a requirement to integrate to other software like Jira or Ranorex, and so the integration capability for TestRail was extremely important for us. And lastly, the reporting capability. To be able to report out to our stakeholders was really important, and we found that TestRail's reporting capability was really powerful. Getting started with TestRail was actually extremely easy, so much easier than most of the other software we implemented. All we really had to do was create a quick how-to guide for those business users that were new to the system, and we literally just did one hour onboarding induction sessions with the software, which got them going pretty easily. We then imported our tests from our previous software directly into TestRail and we were ready to go, to use it on our first project. When we assessed TestRail, we came up with what I suggest is to look at your top three priorities, those must haves for your test management software. So think about... don't focus on what would be nice to have. Focus on what is really important to you. For us it was that functionality around being able to copy and move tests into a regression suite, was our number one. Number two was our user-friendliness of the system, to be able to get people on board really quickly without having to spend hours trying to learn the system, and reporting. So possibly think about those three items as some of your priorities. I also recommend you download the free trial version of TestRail and have a play-around with it and learn how to use it during the free period. That helps you understand the user-friendliness of the system. If reporting is important for you, I suggest you have a look at the reporting feature, because obviously during test phases when you're actually executing your testing, your stakeholders need to be in touch with how your testing is going, so reporting I would say, have a look at the reporting system. Make sure that works for you. And lastly, if direct feedback from your test automation or your defect management integration is an important factor for you, then I also suggest you have a play-around with how it integrates with your automated tools so that you can get that direct feedback back into TestRail.