The initial setup posed certain challenges.

The initial setup of SmartBear TestComplete was complex.

SmartBear TestComplete's deployment phase took 15 minutes.

There is no specific requirement for a technical team to take care of the deployment phase of SmartBear TestComplete since the solution is easy to deploy.

The solution has a simple setup. It's not overly complex. 

Implementation doesn't take too long. It might take about two to three hours in general to deploy.

The initial setup has significant scope for improvement, especially in supporting additional file types and in the area of data comparison. This is why I've rated it as seven out of ten. Certainly, the deployment process involves utilizing an interface pipeline in Azure DevOps that triggers when a new build is available. The TestComplete suite runs in the cloud, generating test results. 

If all scenarios pass, the deployment progresses automatically to other environments like UAT and, if successful there, to production. In case of failure, minimal intervention is required, and the issue is quickly assessed to determine if it impacts the deployment. Critical issues are addressed before further deployment, while minor issues are dealt with internally before proceeding to other environments.

The initial setup is very easy.

The initial setup is pretty straightforward.

The implementation process is hassle-free. I'd rate it a five out of five in terms of ease of installation. It's a very simple process. 

The amount of maintenance needed probably depends upon your project and the number of test scripts you have. It is based on the complexity of your application. If it is straightforward, one person can manage it once it is automated. A larger amount of scripts may require a bit more maintenance, however, something that is low to medium is easy to handle. 

It is easy to install and use.

It was straightforward. Both the node locked and floating licenses were easily deployed, and now the whole team is using it.

At one point, we had to update the hardware of the servers where the licenses were deployed, and this was very easy. We just disabled the licenses from the account and deployed them onto the upgraded servers.

It is very easy to install. It took about one hour to deploy the tool.

The initial setup of this solution was quite smooth. It was not complicated and within a week it was working. It did not take long.

The initial setup was straight forward. No issues at all during the setup stage.

Getting used to product did take some time.

The initial setup was very straightforward. Even the mobile testing side was easy to setup

It is an easy solution to set up. The deployment takes minutes. It's very fast to set up.

We only need one person to maintain the solution. 

The initial setup is pretty straightforward. There's a good license server map for all those things — it's a fairly straightforward solution.

The initial setup was very straightforward. I didn't experience any bugs, glitches, or crashing. I was running 16 tests at one time using half of using my grid and half using the cloud and everything was running fine. I had to test and see if TestComplete could actually go on a Selenium grid and it did.

To start working with TestComplete, we only needed to install (next, next, finish flow) and then start using it. There are some configurations to do to help increase efficiency, but I do not consider that more than a nice-to-have.

StraightForward

Setup is straightforward unless third-party tool integration is required. Integration with Microsoft Team Foundation Server is a little complex for initial configuration. Once it is understood the process is repeatable.

The initial setup of SmartBear TestComplete is easy. The process is almost instant, it is very easy.

The initial setup was straightforward.

It is pretty straightforward. Just by following the instructions given in the document and do the corresponding configuration on the web browsers that you want to test. However, we also encounter some problems such as the Chrome blocking users from proceeding because of an unsafe SSL connection, but we found a work around eventually.

The initial set-up was exceedingly simple. There is a silent mode option available during set-up, which is very convenient when deploying to multiple machines or remotely.

It was very straightforward! You just need to install and begin, no special plugins or out of the ordinary system requirements were necessary.

The initial setup was very straightforward and took very little time.

Set-up was pretty straightforward.

The initial setup was very straightforward. I installed the main app on my local workstation and test execute on five workstations available for testers. We use a shared network drive to store tests.

When deploying new installations of TestComplete, I ran into multiple issues with the licensing engine. The first time I experienced the problem, I contacted support and was directed to a knowledge base article (which I had been unable to find while searching for the error message). I have since bookmarked the article and reference each time I need to do a new install. Once the licenser has installed properly, the configuration and licensing goes smoothly.

The installation is very simple. In just five minutes we can install it and we don't need to do any settings for resetting - such as, for example, how we do it for Selenium or other tools. We don't require much time to deploy it. In no more than five minutes it is installed and ready to go.

The initials setup is not complex at all. It's pretty straightforward. It's easy. A company shouldn't have any problems with deployment.

That said, it might be hard for a normal user. You need to do a few technical things. It helps to have a bit of knowledge on your side. Otherwise, you may run into issues.

You only need one person to set everything up.

Initial setup was very straightforward. We did face some hiccups in license procurement however, once licenses were procured the process from there was quite smooth.

It was very straightforward which was another reason why I went with TestComplete. I was able to use the demo version (when I was searching for options) to create tests easily, so when I had to demonstrate the product to my management teams, they could easily see why TestComplete was the product for us.

The initial setup was straightforward. Licensing was simple, and getting the initial object mapping was painless. Only a high-level base set of object mapping was done.

The setup is pretty easy.

The initial setup is straightforward. We found it simple and not too complex. Our team didn't run into any issues.

For us, deployment took two to three days.

The initial setup was very straightforward. I have a lot of experience and knowledge. Therefore, it was very easy for me to switch to TestComplete, but I am not sure about a new person.

That happened before I was hired, so I don't know.

The previous solution I used was SilkTest, which was being used by my previous employer. It was abandoned because it was hard to script, and advanced features were not being added.

The initial setup is easy. You just have to click and go. It was very fast for me on my desktop, however, I cannot speak to how fast it was on the production server.

The initial setup is not too straightforward and not too complex. I would say that it's okay.

It's not complex.

The initial setup was straightforward. It's a straightforward installation. Deployment took about half a day.

It's quite easy to start using it. There were no problems from the beginning.

The initial set up was not complex. I can say it's straightforward due to the fact that we have started out relatively small. We have gradually developed it. We continue to build it out all the time. That made it simple. This was important for us, as our team didn't have too much experience with the solution. 

The deployment was handled by my IT team. I did not handle the deployment personally.

The initial step was straightforward which was made by carrying out a POC and the decision was to go for this solution.

Initial setup was easy, but implementation was a little tricky initially. I could not find any sample projects that I could use as a guide.

For a node-locked license, it's pretty straightforward. For floating licenses, it's a little more complex because you have to set-up the license manager and do a little bit of configuration on the computers that use the floating licenses.

It was easy.

I would say straightforward, and really easy to work on TestComplete with its simple IDE.

The first was difficult only in learning how to do it. Going forward, it has been easy and intuitive. We scale projects the best way for the company as we find that the simpler way to do it.

The initial setup was easy.

Was it difficult to set up the application first time? No. Or was it difficult to start using it? No, it was easy thanks to its tutorials.

It's straightforward.

It's a simple installation, plus a license key.

We are using the SmartBear suite, which meant that setting up TestComplete was pretty straightforward. As we are still evaluating, it has not been fully deployed.

It was neither straightforward nor complex.

Deploying TestComplete was very easy.

Initial set-up was pretty straightforward, but that was basic. Complexity grows when you go deep in testing.

The initial setup was made easier with professional services. Learning to code was harder.

Installing TestComplete was easy, however "floating license" configuration was challenging with the use of VMs.

The initial setup is as simple as any product with a Windows installer.