We are excited to announce the availability of QlikView November 2018, demonstrating our commitment to maintaining a relevant, dynamic, and highly-functional product for you.

In 2017, a study found that 88% of people will abandon an app due to bugs and glitches. This startling stat demonstrates, with crystal clarity, the need for developers to make their product as clean as possible – with rigorous testing procedures to eliminate any errors. But what are the key steps that go into the testing regime? How can you, as the developer, give yourself the best possible chance of delivering an error-free app?

To me, the best leaders are those that provide transparency in their decision-making process. Every CEO has to make tough calls, but I believe that good leaders influence decisions rather than dictate outcomes. After all, no one likes being told what to do.

API (application programming interface) testing is a type of software testing that performs verification directly at the API level. It is a part of integration testing that determines whether the APIs meet the testers’ expectations of functionality, reliability, performance, and security. Unlike UI testing, API testing is performed at the message layer without GUI.

As more and more businesses look to the cloud to store and manage their data, an increasing number are embracing BigQuery as their serverless, highly scalable, enterprise data warehouse.

This is the second part of my blog series on CI/CD best practices. For those of you who are new to this blog, please refer to Part 1 of the same series and for those who want to see the first 10 best practices. Also, I want to give a big thank you for all the support and feedback! In my last blog, we saw the first ten best practices when working with Continuous integration. In this blog, I want to touch on some more best practices. So, with that, let’s jump right in!