ACCELQ is an agile quality management platform that helps users achieve continuous delivery for web, mobile, manual testing, and APIs. It can be used to write and manage manual test cases for the functionality that may be too fluid for automation.
N/A
PractiTest
Score 8.0 out of 10
N/A
PractiTest is presented as a cloud-based test management tool that provides its customers with an end-to-end system to meet testing and QA needs. It is described by the vendor as flexible but methodological, enabling organizations to ensure visibility and communication at all levels. The solution aims to help users and project development teams streamline and manage their testing processes, while providing management with a clear and simple view of their project status at all times.
$39
user
Selenium
Score 8.3 out of 10
N/A
Selenium is open source software for browser automation, primarily used for functional, load, or performance testing of applications.
Low code test automation, Ready to pickup platform without having much prior knowledge on automation, AI agent interactions are nearly close to real life scenarios, best API automation scale it has got, QGPT logic builder has really changed the talk with DBs in AI way, Logic insights feature is really impressive to identify possible risk while just started developing web apps.
PractiTest works GREAT as a test case repository. It is very easy to gather metrics, filter, and sort based on custom fields. We were able to work with the API to pull our automation results in as well. The support team is always very quick with their responses and monitors the "in-app chat." They are very open to answering questions, providing best practice materials, and looking for additional feedback. If you already have a central location for all of your test cases and testing needs, then I guess you probably wouldn't need to add another. However, PractiTest has high capability and potential, so if it's set up properly you can easily save time managing your tests.
When you have to test the UI and how it behaves when certain actions are performed, you need something that can automate the browsers. This is where Selenium comes to the rescue. If you have to test APIs and not the frontend (UI), I would recommend going with other libraries that support HTTP Requests. Selenium is good only when you have no choice but to run the steps on a browser.
Selenium is pretty user-friendly but sometimes tests tend to flake out. I'd say roughly one out of twenty tests yields a false positive.
Selenium software cannot read images. This is a minor negative because a free plug-in is available from alternate sources.
Slowness may be a minor factor with Selenium, though this is an issue with basically any testing software since waiting on a site to execute JavaScript requires the browser to wait for a particular action.
We love this product mainly because of its high customization abilities and the ease of use. Moreover, its free and can be learned easily through online communities and videos. The tests are more consistent and reliable as compared to Manual tests. It has enabled us to test a large number of features all in one go, which would have impossible through manual tests. The reports generated at the end of the tests are really helpful for the QA and the development teams to get a fair view of the application.
Features like low code, API automation, auto pilot and free account creations, case studies are better suited for my business into IOT space, some of the enterprise automation features are truly game changer in productivity for my team. Database migration was supported seamlessly while opted for ACCELQ solutions.
For those who are unfamiliar with coding, there is a bit of a learning curve. There is plenty of helpful documentation and resources but it can take a little time to get the software up and running. Once you get the hang of how Selenium works, and what it can do, you realize how many things you can use it for, and how many processes you can automate.
The chat button is available to anyone who logs into PractiTest. In my experience, the support has always been very quick, very friendly, and very thorough. They make sure that your question is answered in a way that you understand it. They also provide documentation of best practices so you are never left hanging on what to do next.
The Selenium app has a pretty fat community of users. For the problems we are experiencing, we are primarily receiving support from these communities. In addition, there is widespread service support. Instant support is given to the problems we experience when we need Online support. We and our team are happy to provide this support, especially before important deployment processes
We did everything we needed to use it. Now we can execute our tests on different operational systems and browsers running few tests simultaneously. We also implemented Appium framework to execute our tests on mobile devices, such as iPhones, iPads, Android phones and tablets. We use SauceLabs for our test execution and Jenkins for continuous integration.
When we implemented ACCELQ, we conducted POCs with many similar solutions. Among the tools we pursued at that time, accelQ stood out against Tricentis Tosca and QMetry automation studio. However, subject 7 did better. However, they were still in the nascent stages of building the tool, and hence we did not pick it.
I've used many different Test Case Repository tools, and while each of them has its perks, I like the capabilities of PractiTest best. When creating a test in qTest for example, you can only input information into the fields provided, and you have everything set up in a folder tree structure. With PractiTest, we are able to create custom fields and filter our tests based on those fields to provide more accurate information in a readily available format while quickly searching for the filter instead of through a folder tree. TestRail did not appear to meet our needs as a company. It just didn't have the potential that we found with PractiTest. Zephyr for example worked seamlessly with Jira, which is really nice since that is what we use for the most part. However since we cater to many different clients, we needed an external Test Case repository so we could use something that wasn't tied to 1 Jira instance.
At the time of adoption, there were not many other alternatives that were even close to being competitive when it comes to browser testing. As far as I know now to this day, there is still little competition to Selenium for what it does. Any other browser-based testing still utilises Selenium to interact with the browser.
