Akamai CloudTest vs. Rapise

We were designing an Airlines reservation system, where we wanted to check the maximum number if reservation our system can handle, this tool helped us to get the test results but the issue was from set up point of view, the initial set up took too much time. But we were able to achieve our Reservation system process.

Incentivized

[It's] well suited when there is someone with some degree of programming comfort.

• Integration Call's like REST
• Integration Call's like SOAP
• Performance Testing
• Load Testing on Load Balancer

Incentivized

• Simple recording front-end and easily captures UI objects for later interaction
• Flexible programming interface provides a multitude of manners in which to interact with learned UI objects
• Javascript based IDE is easy to learn

• Report generation is difficult
• Some graphs are not displaying accurate results
• More information are missing with respect to load testing

Incentivized

• For tests that require specific approaches it is necessary to have advanced knowledge of programming in javascrip, which sometimes the QA team does not have experience
• Sometimes I have noticed that when using object dragging errors occur intermittently
• The integration with some tools (Dynamics) is only with the basic functions from my point of view

Incentivized

The bundle of features that other tools provide is much higher when compared to the one provided by Akamai CloudTest, this is something they need to focus on Priority. Most tools comes with default setup and ends to end testing scenario that can be covered, such as Regression testing. From Akamai CloudTest this is a missing features that can be added up soon.

Incentivized

The main reason for choosing Rapise was that the other two options that we had tried at that time only served us for web applications and with Rapise we have greater versatility without changing the solution. In addition to the compatibility with other libraries that are familiar to us and easy application by our team

Incentivized

• System Hangs as where severe load testing is required
• Authentication is an issue when using OAUTH
• Scalability can be improved and also an on premise tool can be of great help

Incentivized

• The primary objective of the institution is a service to the public, so everything that improves response times to the public helps us to achieve it.
• As a department in charge of the development of systems and applications, our objective is fulfilled by delivering quality products and tools such as Rapise help us greatly
• The return on investment can be more than justified by fulfilling the primary objectives

Incentivized