JFrog – The Liquid Software Company.
JFrog has impacted the tech scene working to enable continuous updates through what they call – Liquid Software. They are a major factor in enterprise DevOps initiatives helping organizations bridge software development and deployment. With over 5500 customers, quality and performance are of utmost importance.
We spoke about using Testim with Eli Givoni, QA and Release Manager for JFrog.
In 2016, JFrog was growing fast—very fast.
They believed in quality from the start, building unit and integration testing into the development process. They also recognized the need for functional and end-to-end testing for regression and to validate end-user flows as the JFrog platform expanded, adding new features and revamping the UI experience. Each change meant new tests had to be created and existing tests required updates.
We are always focused on innovation – either releasing a new product or innovating an existing product. That means we need to create a lot of new UI functional tests on an ongoing basis.
Eli Givoni, QA and Release Manager
In order to support the fast scale and growth of its development team and products, they decided to look at test automation solutions that could enable fast authoring, improve test stability and fit their DevOps workflow.
JFrog discovered Testim and decided to do a proof of concept. Eli explained their POC process. “I assigned one of our QA automation engineers to create a suite to test the administration function of the JFrog Artifactory product. He was given five days to get up to speed and complete the task. He was done in two days. This appeared to be a solid ROI.”
When we spoke, JFrog was on the verge of launching a new unified platform that changed the UI of all of its products in one major release.
Creating test coverage while things are in development can be risky. With Testim, we had a big push to create final UI tests. In two weeks we created over 150 new tests in Testim, to enable the successful launch of the unified platform.
Faster test creation. “An experienced QA Automation Engineer could write one or two tests per day in code. They can easily do six or seven per day in Testim.”
Easy to use. “You don’t need to be an expert in Testim to write tests.”
Easy fit into DevOps processes. “We easily integrated Testim into our workflows.”
- Strong support. “The support team at Testim has been a joy to work with—both responsive and helpful.”