It started with a simple question from a friend.
"Bro, is there no proper tool for QA testing? Like something with a UI?"
I paused. I knew about Pytest. Most people do. But then it hit me — you still have to write code to use it. You just wrote a whole app, and now you have to write more code to test the code you just wrote. That felt wrong.
So I said, "Let me look into it." And then — the way these things always go — I just... started building.
The Stack Graveyard (Before We Found the Right One)
I'm not going to pretend the journey was smooth. It wasn't.
Tkinter was the first attempt. It worked, but it felt like showing up to a product demo in a 2003 Dell laptop. Not the vibe.
PyQt was next. The UI was actually decent. But the moment I tried to package it into an installer for delivery, everything fell apart. The engine wasn't being bundled correctly — users were getting a pretty GUI that did absolutely nothing. A software shell with no soul.
Finally landed on Electron + React + Python. This combo clicked. Electron handled the desktop shell, React gave me the UI flexibility I wanted, and Python stayed in the back doing what Python does best — the actual heavy lifting.
What Tron Actually Does
The core idea was simple: 50 pre-built tests, zero extra code required.
When you install Tron, it automatically sets up a conftest file and all the necessary dependencies in the background. You don't configure anything. You don't write anything. You open the app, paste your URL, pick your tests, and hit run.
That's it.
And when the tests finish, you get a proper structured report — not a terminal dump that you have to decipher, an actual readable report you can share.
I called the backend the Tron Engine. Felt right.
Solo Dev Life at a "Company"
Here's the honest part: Systemset Co. is mostly just me.
I give my projects a company name because it helps me take them seriously — it's a mindset thing. But the reality is, I'm one person wearing every hat. Backend, frontend, packaging, documentation, landing page design, Mac builds, Windows builds — all of it.
Getting the Windows installer working was one thing. Then I thought, let me also set it up for Mac, and spent the next however-many hours wrestling with .dmg packaging on top of everything else.
It's a lot. But it's also kind of the best feeling when it actually works.
The Landing Page
I didn't want the landing page to look like it was spit out by an AI in 30 seconds. That meant doing it properly.
Built it in React, and leaned heavily on Aceternity UI, Cult UI, and React Bits for the component design. These libraries genuinely saved me weeks of work. If you haven't explored them yet and you're building landing pages solo — please do.
For the feedback form, I used Formspree. No backend, no database, just a working contact form with captcha that actually sends me emails. Sometimes the boring solution is the right one.
The One Thing I'm Still Stuck On
Code signing.
If you've shipped a desktop app independently, you know the pain. Without a proper certificate, Windows throws a "Unknown Publisher" warning and Mac Gatekeeper gets dramatic about it. The user experience takes a hit before they've even opened the app.
DigiCert and similar services are expensive — we're talking hundreds of dollars per year, which isn't realistic right now for an independent project. I'm looking into alternatives. If anyone has gone through this and found a reasonable path forward, I'd genuinely love to hear it in the comments.
Where Things Stand
Tron is out. People can use it. I don't know yet how many will, or what they'll think of it.
But I built it because the tool I wanted didn't exist. And if even a few other developers find it useful — people who just want to run meaningful tests without setting up a whole testing framework from scratch — then it was worth it.
Check it out: Tron
Feedback welcome. Especially the critical kind.
First post here. Go easy on me — but not too easy.
