The installation of TestRail is not required in its cloud version. With the on-premises version of TestRail, the installation process is straightforward. I did not face any major challenges with the installation part of the product.

The solution's deployment process takes a few hours because of the required configuration, implementation, and testing.

The solution is deployed on TestRail Cloud, which is a public cloud since it's available for anyone to sign up. It is essentially a SaaS product.

Compared to other tools, I rate the ease of setup a seven out of ten.

The initial setup is straightforward.

The initial setup was kind of complex, but I have previous experience that helped. It was not really straightforward. I heard that with the new version, it's in a package and it's not so complex anymore. 

The deployment took around two days. I did the deployment alone and wasn't doing it full time. I did the PoC first and then purchased the license. 

I don't think the initial setup is complex. It is just a Cloud-based system. We need to access the URL and we need to do a single sign-up for it. Since it's an organizational level, we want to maintain security and we need to test identification through a browser and enable the employee profile in the Cloud. That's it.

When we did the initial level POC, we did it on Cloud for the pre-trial version. But since our organization is a healthcare level, we took TestRail and configured it for our own use On-Premise.

There are a lot of Okta authentication there. It is a two-factor authentication. So, the moment when we are associated with that kind of app, it connects to the TestRail wherever they're hosting a server. It is kind of an exchange of data through the Okta app for security authentication.

The product's setup is straightforward. The tool's setup takes only a couple of minutes to complete. You need to look through the training material and follow it. 

TestRail's deployment was easy. 

The initial implementation took us approximately one week. We built the workflow, integration, and everything else. We optimize the process as we go.

The initial setup is straightforward but customization can be complicated. 

The initial setup is quite straightforward.

It takes hardly 10 to 15 minutes to do the initial setup.

We have only one team which maintains many tools across the organization and they take care of this solution.

I don't have any experience setting it up on-prem. I've done it on the cloud which was very easy. It only took five or so minutes. 

The tool's deployment was completed in a day. 

I didn't do the implementation myself. It was already done when I arrived at the company. I just manage the users. I switch users and accounts when someone leaves the project or joins. Being a cloud version, however, I imagine it's fairly easy to configure.

Setup was pretty straightforward. Creating our own customized reports was more complex. It required writing PHP code and they are time consuming to maintain.

I wasn't involved in the setup. I QA'd the app, and indicated to the administrator what I desired.

Not applicable. It was already set up when I joined.

I rate the initial setup process a nine out of ten. It takes 20 minutes to complete.

I did not manage it myself, but it seemed straightforward (using the officially supported Linux version).

The initial setup was straightforward.