Qase Blog

Black box and white box testing are distinct methodologies with opposing objectives. However, they can complement each other to improve testing effectiveness. Black box testing evaluates an application from the user's perspective, while white box testing examines the code and internal design. This article explores both methods, their types, techniques,

Example mapping is a technique to help give shape to your requirements. Explore this visual and written guide to learn how it works and how to use it.

Automated tools tend to promise programmers and development teams faster, more efficient workflows, but relying solely on automated code review tools won’t guarantee you high-quality code. Automated code review is the process of using software tools to automatically analyze source code for issues such as bugs, security vulnerabilities, and

Code review is a standard part of the software development process in many companies, but in many cases performing code reviews is inefficient or even illogical. For this article, I’ll focus on only pull-request-based code reviews. With pull-request code reviews, a developer works on some code and then sends

Hi, I’m new here! I’m Jenna Charlton, US-based Developer Advocate at Qase. A little background Where I live: The suburbs of Cleveland Ohio on the shore of Lake Erie Where I grew up: Shaker Heights Ohio (yes that Shaker Heights, it’s a real place) Where I went

Explore the practice of dogfooding and learn how it can positively impact software and product development across industries.

What is Behavior-Driven Development? When creating software, particularly new products, a diverse set of individuals is involved, including business and product owners, developers, testers, and QA engineers. Often, these stakeholders perceive the end result differently. Managers and marketers focus on business objectives and user satisfaction, developers work within technical and

Qase has raised a total of $7.2M in Series A and seed funding rounds to accelerate our pursuit of helping QA teams increase their testing efficiency and speed.

“Five whys” is known as a simple way to get to the root cause of a problem — but the simple methodology is better suited to simple problems rather than complex ones. Quality Assurance requires analyzing incidents and taking measures to prevent them in the future, and that analysis often requires