What is our primary use case?
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.
How has it helped my organization?
The major thing it has helped with is to reduce the workload on testing activities. This was the major reason for going with Silk Test. The people are happy using it and the end results are provided in a short span of time.
Our deployment process is not very long, where one automated process takes approximately one to two weeks to complete a six hundred step manual test case.
What is most valuable?
The most valuable feature is the recording capability, which is something that the business users can start learning and using in a day. The technical people are not really required to use this. It is quite simple and easy.
This user interface is quite easy and something that everybody is able to follow.
It has a feature that saves the previous version so it is easy for deployment to just move the current version to the production environment.
What needs improvement?
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.
For how long have I used the solution?
What do I think about the stability of the solution?
I have been using Silk Test since version 15. When I used it, it was a really good solution but there is still a lot that can be improved.
What do I think about the scalability of the solution?
It is quite scalable and this has to do with the licensing. It is not a tedious process.
We use this solution internally with the IT team, of which there are twelve to fifteen members. They perform all of the necessary actions and changes, and the reports will be shared globally with the top management.
We do plan to increase our usage. Just recently we procured an additional twenty-four licenses and have seen the benefits. In the future, I foresee that we may purchase licenses for an additional thirty users.
How are customer service and support?
With respect to technical support, anytime we have reached them and received a ticket, we get a response within twenty-four hours. It's quite good, and in cases where they were not able to clarify they reschedule our call based on a convenient time.
Which solution did I use previously and why did I switch?
We had been using Panaya four to five years ago, and we want to bring that back since our business users are comfortable with it.
I have used SAP TAO previously but that was in another organization. We used it as a build automation tool for UFT. Silk Test is a simpler tool that I retrained myself to use.
How was the initial setup?
The initial setup was straightforward because the vendor, Micro Focus, really helped us in setting up the environment. It was not too complex.
With respect to the deployment, two or three people can handle it. The developer is the one who is responsible for all of the source code management, and the admin takes responsibility for the deployment. These two roles are more than enough for this implementation.
What about the implementation team?
We used the vendor, Micro Focus, for the implementation. They gave us two or three weeks of training, which was good. Initially, they supported us, and we didn't go for any external support.
Our deployment took around two to three weeks. We implemented a role-based strategy with restricted access so that not everybody will have access to the files.
What's my experience with pricing, setup cost, and licensing?
Our licensing fees are on a yearly basis, and while I think that the price is quite reasonable I am not allowed to share those details.
Which other solutions did I evaluate?
Before choosing this solution there were a few other products that were evaluated. Some of these were Worksoft Certify and SAP TAO. The latter was evaluated for a second time, but we still chose the Silk Test solution.
What other advice do I have?
I would definitely recommend implementing this solution but make sure to get the necessary authorization. Ask about the service assistant and check with the other users as well.
You have to make sure that you get all of the deliverables that have been maintained in the statement of work that has been described, otherwise, you might miss something and get into trouble. It's better to look at the agreement, see what the deliverables are and make sure that everything has been completed before they hand it over. Otherwise, it will be a really difficult problem to handle.
The features that are currently available are useful for everyone, but there are a lot of improvements that they need to do. The basic functionality to support artificial intelligence is there, but it can still be improved.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
*Disclosure: I am a real user, and this review is based on my own experience and opinions.
Hi Malli!
Thank you very much for your review!
I have some questions left:
1. If you guys liked Panaya and want to change back to it, why do you prefer it over Silk Test?
2. What Silk Test client did you use? (Silk4j, Silkl4NET, Silk Workbench)
3. You said, there is a lot that could be improved. What exactly did you refer to, if you can say that?
4. If the support re-scheduled a call, how long did you have to wait to receive an answer then? More than one day?
Thank you very much :)