To set up Silk Test, you have to take the licenses of the product and configure them onto your server. From there, you can install Silk Test. You should have access to the applications which you are going to test.

In terms of the application manuals, the application needs to be performance tested from various IP's. Other than that, it's a simple, straightforward installation. 

Deployment takes about a month.

It was done before my time.

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.

The initial setup was somewhat complex. 

The initial setup is straightforward. We didn't find it complex at all. Deployment took about 30 minutes in our case.

Setup in general is pretty easy. There were 2 major issues we could encounter:

1) In addition to base technologies we had to enable extensions to support ActiveX, Web and some other UI types. And extensions could be picked up after some retries which wasn't really convenient

2) Not sure about now but SilkTest was hard to work on machines which had Mercury (later acquired by HP) products installed (WinRunner, QTP or LoadRunner). Usually problem appeared with extensions. They couldn't be enabled

The difficulty of the integration will depend on whether you are using it as a single user or as a part of a community of users. Integrating for a single user is very simple. If you use it as a part of a community of users you have to understand the SQL setup. It's a little bit more difficult. 

Single user deployment will take around five minutes. The best way to use it is with a central database so lots of people can use it. You have to structure the database and your projects carefully. It's not straight out of the box. You have to do a lot of thinking about how the products and projects are structured in the database. 

The initial setup was fairly simple but quite stressful. It's supposed to support the strategy but as soon as you know what you're doing, it becomes easier.

While I can't say that the setup was complex, the integration with Silk Central / Git was particularly painful, especially due to the fact that the fields in Silk Central have weird naming that don't sound identical to the naming used by Git/GitHub repos.

It was a straightforward set-up.

It was straightforward.

It was straightforward.

It was straightforward and we did not encounter any issues.