HeadSpin vs. Liquibase

We have been using HeadSpin for our web and mobile application testing. It is an easy-to-use solution that provides detailed and in-depth analytics from the testing results. We also get a wide range of live networks and devices to perform the testing from HeadSpin. It has an inbuilt artificial intelligence engine that helps us to get real-time scenarios simulated, which is very helpful for finding performance issues and improving the overall quality of the applications.

Liquibase is well suited when there is a need to manage database version. When there are database changes then Liquibase can easily manage, deploy the updates and it can build an automated CI/CD pipelines for databases. Liquibase is less appropriate where there is no change in database schema but that is less likely to happen.

Incentivized

• Keep track of each browser we have tested and when we lastly updated them.
• Remove any deprecated code or plugins that may cause issues with other browsers.
• Add browser information to our site’s meta tags so that the site displays correctly in different browsers.
• Test our website on all browsers to ensure compatibility.

• It's a useful tool for managing database versions and aiding in the development of database CI/CD pipelines.
• The deployment and management of database updates are simple.
• It provides quality checks to spot problems in DB scripts and DB pipeline views to track changes made to DB.

Incentivized

• UI needs to be improved
• Graphs on the dashboard are a bit laggy and need detailing for a better understanding of the user

Incentivized

• Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9
• We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase
• Liquibase should rollback the if any one of the changes fails.

Incentivized

We are and will continue using Liquibase and it has become an integral part of our portfolio offering, any new product is by default adopting Liquibase stack.

Incentivized

Build process is too time consuming and getting extra DB instance takes a toll

Incentivized

The support is the only issue they took several hour to respond a simple EMail I believe that this is because of the Time Zone difference. By the time that they respond we already have solve our issues. Another issue is they close the support tickets some time before confirm that the question is solved. They are more focus in close tickets to reach the SLA that in give a real support

Incentivized

the database deployments helped us with increased productivity,
faster delivery and low risk.

Incentivized

Though LambdaTest was cheaper, it did not offer the deal devices and we wanted to be 100% sure that our app offers a perfect experience to all users. Simulators and emulators are not the technology we wanted to rely on.

There is no real competitor when it comes to what Liquibase does - at least not at the time we considered it three years ago. It was an easy choice in this regard, but we could have said no to it if it made our workload more difficult. But our proof of concept showed there were easy wins to be had by implementing its software.

Incentivized

• Simplified the approach to test the mobile application on multiple devices from different vendors. This helped us to ensure the stability of the application in different environments.
• In-depth analysis to understand the loopholes in the application design function. This helped us to improve the application design and overall user experience.

Incentivized

• We need to re-educate developers to use Liquibase.
• In some cases, it is hard to align when several teams work on the same DB.
• On the other hand, Liquibase provides order and consistency in managing DB changes.
• Evidence and traceability are a plus.

Incentivized