Tomcat is an open-source web server supported by Apache.
N/A
Tricentis qTest
Score 8.3 out of 10
N/A
Tricentis qTest (formerly QASymphony) provides enterprise-level agile testing tools giving businesses visibility and control needed to ensure application quality in fast-paced development environments. Tricentis and QASymphony merged in summer 2018.
Excellent value for companies wishing to host Java applications in the cloud. Utilizing hosting tools such as load balancers and network and application firewalls, Tomcat can be part of a powerful system to host web applications to thousands of users. There has been consistency in the development and support of Tomcat since its initial release in the late '90s and the best commonalities have been carried forward. If you host Java web applications, Tomcat is as good as any for an application server.
The qTest is well-suited for organizations transitioning to Agile or DevOps frameworks. It Streamlines test management with real-time collaboration and integrates with popular CI/CD tools. It excels in complex, large-scale projects needing centralized test cases management, traceability, and detailed reporting. However, organizations on a tight budget might find it cost prohibitive compared to simpler, low-cost alternatives.
Highly customizable: we were able to organize our test cases in unique ways that made our work easier.
Connectivity with Jira: being able to pull requirements information in from Jira was a big point for us.
Standalone tool: Being a standalone tool on a dedicated server, we were able to have access to our tests regardless of whether our Jira server was down.
Using tomcat manager to troubleshoot is not very informative. Error messages are vague, you have to dig into log files for more information about the problems.
Is great for simple web applications, but may not work for heavy development which may require a full J2EE stack, might like JBoss better.
Security in tomcat is not straightforward, as I discovered that you have to understand how to set up realms in tomcat in order to hash passwords, which I was not overly familiar with, which is a big deal when setting up users in the tomcat-users.xml file.
In requirements , we can't add multiple test cases at once, or search multiple cases at once, need to do one by one. Here actually qtest needs to improve.
Linking cloud hosted qtest and on-premise TOSCA is very difficult especially when you are working with client system with security wall. It requires tunnelling software which is not recommended.
Tomcat has a very rich API set which allows us to implement our automation script to trigger the deployment, configure, stop and start Tomcat from the command line. In our projects, we embedded Tomcat in our Eclipse in all of the developer's machines so they could quickly verify their code with little effort, Azure Webapp has strong support for Tomcat so we could move our application to Azure cloud very easy. One drawback is Tomcat UI quite poorly features but we almost do not use it.
Tomcat doesn't have a built-in watchdog that ensures restart upon failure, so you have to provide it externally. A very good solution is java service wrapper. The community edition is able to restart Tomcat upon out of memories exceptions.
Tomcat support to customize memory used and allow us to define the Connection pool and thread pool to increase system performance and availability, Tomcat server itself consume very little memory and almost no footprint. We use Tomcat in our production environment which has up to thousands of concurrent users and it is stable and provides a quick response.
Eclipse Jetty is the best alternative for Apache Tomcat because which is also an open-source and lightweight servlet container like Tomcat. A major advantage of this over Tomcat is that Jetty server can easily be embedded with the source code of web applications. Since it requires less memory to operate, you may realize that it is very efficient.
Extensive integration options with various third-party tools, enabling seamless integration into existing workflows. Allows for flexibility and customization of workflows, fields, and permissions to adapt to unique testing requirements. Supports robust requirements traceability, ensuring comprehensive test coverage. Lastly management decisions too
Tomcat is cheap and very quick to deploy, so it has benefited much when situation needs applications to be deployed quickly without wasting time on licensing and installations.
Plenty of documentation available so no vendor training is required. Support contract is not needed as well.
Better organization and centralization of test cases has led to more cohesive team collaboration
Speed to delivery, deployments to production, are mostly maintained
Performance issues have led to testing delays requiring the team to switch to other methods which contributed to QA bottleneck issues and sometimes even missed sprint commitments
