Systems | Development | Analytics | API | Testing

At Qlik, we’ve always done things a little differently. Maybe it’s our Swedish heritage. Maybe it’s our relentless curiosity. But for us, “different” doesn’t just apply to our platform — with its unmatched breadth and flexibility — or our people, who bring world-class guidance and support to every customer and partner we work with. It’s a mindset that runs through everything we do, including how we approach our biggest event of the year: Qlik Connect.

When you write code, how do you know it actually works? You could run the program and click around manually—but that quickly becomes tedious, unreliable, and error-prone, especially as your codebase grows. That’s where unit testing comes in. Unit testing lets you verify that individual pieces of your code—like functions or methods—behave exactly the way you expect.

New features ship weekly. Designs change overnight. Releases go out daily. But speed comes with risk, and when your UI is broken, users don’t care why. They just leave. That’s where automated UI testing comes in. Done right, it protects the user experience without slowing you down. Done wrong, it becomes flaky, expensive, and hard to maintain.

Gathering requirements in an Agile environment can feel like a balancing act, especially if you're operating in a heavily regulated industry. While the collaborative and iterative nature of an Agile approach facilitates productive and efficient workflows, it can make gathering and tracking requirements difficult. In the rush to complete a sprint, it’s easy to lose sight of user stories and the corresponding acceptance criteria. Three reasons Agile teams struggle with requirements gathering include.

The goal of any mobile product is to create an app experience that’s innovative and new. But you must accomplish specific, necessary steps between crafting a clear vision for your app and creating a mobile application which is where a mobile app testing strategy comes in. Today, mobile app testing encompasses a vast array of coverage areas, including functional testing, usability testing, performance testing, security testing, compatibility testing, and more.

That's a lot of tests.

Software quality assurance has evolved significantly in recent years, with behavior-driven development (BDD) emerging as a powerful methodology for aligning technical teams with business objectives. At the center of this evolution sits Gherkin, a simple yet powerful specification language that bridges the communication gap between technical and non-technical stakeholders and simplifies the creation and maintenance of automated tests.

Joined by hundreds of QA experts around the globe, Quality Horizon was truly a remarkable event, where a lot of thought-provoking conversations were sparked. We believe that participants of the Summit have taken home many actionable insights to improve their day-to-day work. If you haven't had the chance to join the summit, here's a quick recap. There were 5 sessions in total: Let's dive in!

The Centers for Medicare & Medicaid Services (CMS) has taken a key step toward improving healthcare efficiency and transparency. Under the CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F), payers must offer electronic access to prior authorization (PA) information.

Software testing is essential in delivering high-quality applications. It plays a crucial role in maintaining user trust and satisfaction.