Director of Engineering at a energy/utilities company with 51-200 employees
Real User
Jan 6, 2021
We used it for data-driven automated tests that have numeric calculations with high precision requirements. We probably are using the version from two years ago.
Director Consulting Expert at a computer software company with 10,001+ employees
Real User
Feb 6, 2020
I primarily use the solution for performance testing. It can also handle capacity planning on web applications. Silk Test is a tool with which we can simulate the number of users, and with that, ramp up and ramp down strategies that we can design. Based on the load model we can design performance tests for our applications. On top of it we can do configurations. We test the solution to PPS. For example, we test how many PPS transactions per second will be simulated on Silk Test. We can find out how much time testing will take. You can integrate various performance tests, which typically takes one hour. We can do stress tests, and, within an hour, we can then test it. Sometimes, we help test the tool for as long as 36 hours to see how exactly the application can be implemented, in case of any memory loss. When we did the applications related to performance, we design the load normally. When we try to understand the various critical performance test scenarios, using Silk Test, we record them. Afterward, we handle the configurations. According to the results, we trigger. Once we trigger data, we try to observe the behavior of the application, as the tool now simulates the load. We look at the responsiveness and note that the response times are getting increased. We also try to see what kind of behavior changes are happening within the application. We'll look at whether the hardware resources of the application are going up, or if memory is going down. We look for problems or memory loss. Once we've finished testing, and observe everything, we'll try to do our engineering and work to uncover loopholes that may impact the application's performance. Everything will be recorded and investigated. We'll explain our findings to stakeholders and explain what needs to be done going forward.
We predominantly use the solution for network performance testing. We are currently deploying a solution to various countries in Africa, so we're predominantly using it for current applications.
IT Service Delivery Manager Testing and RPA at a transportation company with 1,001-5,000 employees
Real User
May 15, 2019
Our primary use case for this solution is regression testing which is done every month end. We have a management cycle specific for SAP where a few changes will be moving to prediction. There are approximately one to two hundred scenarios where that needs to be executed. Our regression test makes sure that the functionality is not being affected at any point in time. We also use it for automation testing in non-SAP projects that have problems internally detected by our team.
SilkTest is robust and portable test automation for web, native, and enterprise software applications. Silk Test's portability enables users to test applications more effectively with lower complexity and cost in comparison to other functional testing tools on the market. Silk Test's role based testing enables business stakeholders, QA engineers, and developers to contribute to the whole automation testing process, which drives collaboration and increases the effectiveness of software testing.
The product is used for manual, functional, and performance testing. I'm using the tool for loading data into ERP systems.
We are customers of Silk Test and I'm the IT QA manager
We used it for data-driven automated tests that have numeric calculations with high precision requirements. We probably are using the version from two years ago.
I primarily use the solution for performance testing. It can also handle capacity planning on web applications. Silk Test is a tool with which we can simulate the number of users, and with that, ramp up and ramp down strategies that we can design. Based on the load model we can design performance tests for our applications. On top of it we can do configurations. We test the solution to PPS. For example, we test how many PPS transactions per second will be simulated on Silk Test. We can find out how much time testing will take. You can integrate various performance tests, which typically takes one hour. We can do stress tests, and, within an hour, we can then test it. Sometimes, we help test the tool for as long as 36 hours to see how exactly the application can be implemented, in case of any memory loss. When we did the applications related to performance, we design the load normally. When we try to understand the various critical performance test scenarios, using Silk Test, we record them. Afterward, we handle the configurations. According to the results, we trigger. Once we trigger data, we try to observe the behavior of the application, as the tool now simulates the load. We look at the responsiveness and note that the response times are getting increased. We also try to see what kind of behavior changes are happening within the application. We'll look at whether the hardware resources of the application are going up, or if memory is going down. We look for problems or memory loss. Once we've finished testing, and observe everything, we'll try to do our engineering and work to uncover loopholes that may impact the application's performance. Everything will be recorded and investigated. We'll explain our findings to stakeholders and explain what needs to be done going forward.
The solution is generally a framework for test functional automation. We use it for automation of web applications for the most part.
We predominantly use the solution for network performance testing. We are currently deploying a solution to various countries in Africa, so we're predominantly using it for current applications.
Our primary use case for this solution is regression testing which is done every month end. We have a management cycle specific for SAP where a few changes will be moving to prediction. There are approximately one to two hundred scenarios where that needs to be executed. Our regression test makes sure that the functionality is not being affected at any point in time. We also use it for automation testing in non-SAP projects that have problems internally detected by our team.