SmartBear LoadNinja presented issues around some use cases that we wanted to do. We were using the solution to simulate using a browser and to give some browser access to our use case for multiple users. We faced some issues when all the servers going behind took a lot of time when we ran those tests. Although the results were pretty good, the real-time results were not. If there's an issue in a certain machine running in that test, we did not get the result of how the Chrome browser responds to our application. There were some difficulties in our test cases that we wanted to have around the results that we wanted. As we ran the test, we couldn't see the real-time results of how the solution behaved for 200 to 400 virtual users.
Test Manager at a tech services company with 51-200 employees
Real User
Top 5
2022-11-04T10:59:18Z
Nov 4, 2022
It's a new tool when I compare it with LoadViewer and HP LoadRunner. It needs time to mature. For example, it needs to improve concurrency. When you run a test suite, your scripts will generate some test data. If we are running a banking application and then we are running a full end-to-end suite, there are many actions that need testing. There's a lot of data getting generated. There should be a variable that we can store for later in our later test cases. We need data management and dynamic data generation to be able to capture the data which is generated.
The cost could be reduced slightly. On a smaller scale, there will be no budget issues, but as we expand to a larger user base, I believe we will face some pricing challenges.
What are performance testing tools? Before an application can be deployed, it should ideally be tested under different operating conditions to make sure it can perform as expected. To do this, software testing professionals use performance testing tools (sometimes just called “testing tools”) to isolate and identify potential client, network, and server bottlenecks that might affect how an application will behave in production.
Some performance test products are commercial....
SmartBear LoadNinja presented issues around some use cases that we wanted to do. We were using the solution to simulate using a browser and to give some browser access to our use case for multiple users. We faced some issues when all the servers going behind took a lot of time when we ran those tests. Although the results were pretty good, the real-time results were not. If there's an issue in a certain machine running in that test, we did not get the result of how the Chrome browser responds to our application. There were some difficulties in our test cases that we wanted to have around the results that we wanted. As we ran the test, we couldn't see the real-time results of how the solution behaved for 200 to 400 virtual users.
It's a new tool when I compare it with LoadViewer and HP LoadRunner. It needs time to mature. For example, it needs to improve concurrency. When you run a test suite, your scripts will generate some test data. If we are running a banking application and then we are running a full end-to-end suite, there are many actions that need testing. There's a lot of data getting generated. There should be a variable that we can store for later in our later test cases. We need data management and dynamic data generation to be able to capture the data which is generated.
The cost could be reduced slightly. On a smaller scale, there will be no budget issues, but as we expand to a larger user base, I believe we will face some pricing challenges.