I wrote a test management app.

I wrote a test management app. I know that's a cliche these days, everyone's using AI to write an app. The difference is, I have ~20 years experience testing software development.

I recently got made redundant and I got bored waiting for more AI-generated rejection emails while I’m hunting for a new job, so I decided to do something useful with Google Antigravity as a learning exercise and to keep the old braincells working. I’ve never been a fan of daytime TV.

I started with a docker container for Postgres and the standard template project for a blazor/c# web application from Visual Studio – then I used the Antigravity agent manager to make iterative changes. I moved from MS SQL to Postgres straight-away and I created a data audit tool. So every data change is logged to a data audit table along with the user that made the change. I implemented role-based security and authority, optional 2FA and internationalisation. On the second day… I’m kidding, this has taken me a few weeks to pull together. I haven’t been working on it full time, even with a Google One account you sometimes have to wait five hours for your AI credits to refresh.
Architecture-wise it’s quite conservative:
PostGres DB /.Net Core back end in c# / blazor front end – I have avoided python and node, which the tools were trying to push me towards.
I’m running in docker on my local machine, I have a test and a preprod environment an a github CI/CD pipeline with a local runner running as a service on my local machine. I have MStest unit tests and Playwright tests built into the pipeline – the Playwright tests only run on the preprod pipeline.
Setting up and playing with these tests was the main reason for me to build this application, and I have some more work to do setting these up, they are more proof-of-concept place holders than full-fledged tests at this stage.
Feature-wise:
Dashboard – as shown above
Projects – that can pull details from Jira tickets:

Test Suites – within projects that can be imported or exported with CSV files

Test Cases – with test steps

Test Runs – where you step though each test case step in a selected test suite one step at a time and you can create a bug at any point:

Bugs

Bugs can be used to create bugs in Jira

User Management – allows administrators to define users and roles:

Audit report – allows administrators to list all the data changes to the database:

Admin Settings – allows administrators to set global parameters like Jira and translation API keys and language settings:

You can find it on Github, it is open source - Loretest Github Repo