Likelihood to Recommend
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.
Read full review
It is well suited when test execution status have to shared with management in real time, modifying and executing of the tests is really simle, I personally like the comment section where any images can be easily uploaded. If they just make the navigation better it will be a good option in test case management
Read full review Pros Fast to start up, which is useful when we need to just check that our changes are working correctly. Free, which allows us to not be involved with the finance/legal team about using it. Bundled with Spring Boot, which makes it even more convenient for our testing. Read full review 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. Read full review Cons 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. Read full review 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. Read full review Likelihood to Renew
We have a huge knowledge of the product within our company and we're satisfied with the performance.
Read full review
This has been a core QA management tool for our organization and integrates well with our other SDLC platforms (Azure DevOps/Jira/Katalon).
Read full review Usability
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
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.
Read full review
qTest is actually intuitive and user-friendly, despite my other scathing review aspects
Read full review Reliability and Availability
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.
Read full review Performance
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.
Read full review Support Rating
Well, in actuality, I have never needed support for Apache Tomcat since it is configured and ready-to-go with no configuration needed on my end.
Read full review
The actual answer is 0. I have never experienced worse support, whether personal or professional
Read full review Implementation Rating
Again, supporting documentation could have been a lot better
Read full review Alternatives Considered 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.
Read full review TestRail
is slow as compared to qTest. The color combinations used in
are quite confusing and the UI looks scrunched.
's navigation and search are also quite complicated as compared to qTest.
's Analytics is undesirable as it is unable to generate project specific reports, users can only see the test plan progress whereas qTest includes various project related metrics as well.
Read full review Scalability
It's very easy to add instances to an existing deployment and, using apache with mod proxy balancer, to scale up the serving farm
Read full review Return on Investment 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. Read full review 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 Read full review ScreenShots Tricentis qTest Screenshots