Inspiration

As a software tester, I really like good processes and an intuitive, well-crafted UI. I was always looking for a great QA tool that connects to the development lifecycle fluently, and actually helps software teams to overview and control quality in their releases. Evaluated and used multiple testing tools and decided to create a new one, based on my best practices of a decade. A tool, which is great in usability, answers many questions instantly when they pop up, and is still really simple to get started with. This app was named BestTest, hopefully one of the best tools supporting QA and dev teams in their relentless work, crafting a wonderful piece of software. In today's rushing world ;)

What it does

In BesTest, users can create and manage Requirements - to gather what actually should be developed, based on what. This resonates with JPD's Idea collections, but Requirements are more like strictly decided elements, which are planned to be created in the near future, and should be accountable during release. A Requriement Test Cases can be created and linked to Requirements, so that you can set up proper coverage. The app helps the user with the expected number of test cases. Test cases go through a review process, which is a great way to preserve trustworthy Test Collections. Test cases can be executed via Test Cycles, where multiple testers can record execution results in parallel. Executions Test Managers will be curious about Reporting features, of which the app currently has 5. These reports are handcrafted, and should answer the most popular questions like how is the progress, when are we gonna finish, and is this something important we missed during our QA process? Reporting Also, bugs are connected during the testing process, and reports covering the progress of connected bugs are also available.

How we built it

The app has solid foundations on Atlassian's Forge platform. Frontend using React and TypeScript, and the development was iterative until the deadline arrived. In the practical part, ISTQB was a solid foundation to build on top of.

Challenges we ran into

It is actually really hard to build a meaningful initial release, while not building all the planned features! The backlog is so long that it was really hard to reduce scope, but it still provides enough value to be worth trying. Starting a complex app in the Atlassian Marketplace in 2025 is really challenging.

Accomplishments that we're proud of

The UI of the app was built similarly to Jira's latest design, which makes the average user think they are using Jira itself. I believe this should be the way apps are implemented in an ecosystem like this. Also, there is a dark theme support, which is really lovely!

What we learned

The great possibilities to build on top of Forge and the infinite feature ideas were inside us.

What's next for BesTest - Requirement & Test Management

After initial release, the app will introduce import features to make it easier to move in. Will add many QOL features, an API for Test Automation, and a Release Hub where users will be able to understand how their release goes. All feedback is welcome!

Share this project:

Updates