Manager QA at a tech vendor with 1,001-5,000 employees
Real User
2021-10-12T14:11:42Z
Oct 12, 2021
The initial setup is somewhat complex if you're deploying on-prem. It means we have to set up a database and application client machines, as well as Silk Meter which manages the licenses. It could be more user-friendly on the installation and configuration side.
Director of Engineering at a energy/utilities company with 51-200 employees
Real User
2021-01-06T08:49:40Z
Jan 6, 2021
We moved to Ranorex because the solution did not easily scale, and we could not find good and short term third-party help. We needed to have a bigger pool of third-party contractors that we could draw on for specific implementations. Silk didn't have that, and we found what we needed for Ranorex here in the Houston area. It would be good if there is more community support. I don't know if Silk runs a user conference once a year and how they set up partners. We need to be able to talk to somebody more than just on the phone. It really comes right down to that. The generated automated script was highly dependent upon screen position and other keys that were not as robust as we wanted. We found the automated script generated by Ranorex and the other key information about a specific data point to be more robust. It handled the transition better when we moved from computer to computer and from one size of the application to the other size. When we restarted Silk, we typically had to recalibrate screen elements within the script. Ranorex also has some of these same issues, but when we restart, it typically is faster, which is important.
While we are performance testing the engineering key, we need to come up with load strategies to commence the test. We'll help to monitor the test, and afterward, we'll help to make all the outcomes, and if they are new, we'll do lots and lots of interpretation and analysis across various servers, to look at response times, and impact. For example, whatever the observations we had during the test, we need to implement it. We'll have to help to catch what exactly is the issues were, and we'll help to see how they can be reduced. Everything is very manual. It's up to us to find out exactly what the issues are. The solution needs better monitoring, especially of CPU.
IT Programme Manager at a financial services firm with 10,001+ employees
Real User
2020-02-06T11:37:16Z
Feb 6, 2020
The solution has a lack of compatibility with newer technologies. When tests are recorded on to Silk Central, there is a bit of a lack of clarity in terms of what needs to be fed into Silk Central and how the test cases and reports are all managed. The solution should make it easier to schedule our test cases during out of office hours. We want the solution to allow us to do more of API level integrations.
The integration of the object library can be improved. It's a bit clunky. It also has some commands that are difficult to use sometimes. We work around its deficiencies and forget that it's a deficiency. They should extend some of the functions that are a bit clunky and improve the integration.
IT Service Delivery Manager Testing and RPA at a transportation company with 1,001-5,000 employees
Real User
2019-05-15T05:16:00Z
May 15, 2019
The product has a lot of features, but many of the clients do not know how it can improve their productivity. Information on how these features can be used would be helpful. The support for automation with iOS applications can be better.
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 pricing could be improved.
The initial setup is somewhat complex if you're deploying on-prem. It means we have to set up a database and application client machines, as well as Silk Meter which manages the licenses. It could be more user-friendly on the installation and configuration side.
We moved to Ranorex because the solution did not easily scale, and we could not find good and short term third-party help. We needed to have a bigger pool of third-party contractors that we could draw on for specific implementations. Silk didn't have that, and we found what we needed for Ranorex here in the Houston area. It would be good if there is more community support. I don't know if Silk runs a user conference once a year and how they set up partners. We need to be able to talk to somebody more than just on the phone. It really comes right down to that. The generated automated script was highly dependent upon screen position and other keys that were not as robust as we wanted. We found the automated script generated by Ranorex and the other key information about a specific data point to be more robust. It handled the transition better when we moved from computer to computer and from one size of the application to the other size. When we restarted Silk, we typically had to recalibrate screen elements within the script. Ranorex also has some of these same issues, but when we restart, it typically is faster, which is important.
While we are performance testing the engineering key, we need to come up with load strategies to commence the test. We'll help to monitor the test, and afterward, we'll help to make all the outcomes, and if they are new, we'll do lots and lots of interpretation and analysis across various servers, to look at response times, and impact. For example, whatever the observations we had during the test, we need to implement it. We'll have to help to catch what exactly is the issues were, and we'll help to see how they can be reduced. Everything is very manual. It's up to us to find out exactly what the issues are. The solution needs better monitoring, especially of CPU.
The solution has a lack of compatibility with newer technologies. When tests are recorded on to Silk Central, there is a bit of a lack of clarity in terms of what needs to be fed into Silk Central and how the test cases and reports are all managed. The solution should make it easier to schedule our test cases during out of office hours. We want the solution to allow us to do more of API level integrations.
The pricing is an issue, the program is very expensive. That is something that can improve.
The integration of the object library can be improved. It's a bit clunky. It also has some commands that are difficult to use sometimes. We work around its deficiencies and forget that it's a deficiency. They should extend some of the functions that are a bit clunky and improve the integration.
The product has a lot of features, but many of the clients do not know how it can improve their productivity. Information on how these features can be used would be helpful. The support for automation with iOS applications can be better.