Tuesday, March 31, 2015

As you can probably see from the sidebar, my efforts to consolidate Testopia are almost completed. 95% might be pushing it a bit (most of the files are still awaiting approval), but I believe that the workload left will be minor fixes.

Now I've got the hard one ahead of me, updating the framework. Regardless of the framework I choose, it's going to be a long learning experience, but I'm going to supplement the process with general fixes.

Wednesday, March 4, 2015

Quick update.

I have a few concepts brewing around in my head. While I never got as far as writing a design document for any of them, I’m going to try to do it in the next week.

GDC’s multiple engine announcements really threw me for a loop. I may need to spend some time investigating some of these new offerings.

Monday, December 29, 2014

Resolutions for 2015

1) Release at least one game.

I know this is a resolution I make every year to no success, but I've got a good feeling about this year.

2) Bring Testopia up-to-date

As my focus has shifted from "update an aging Bugzilla system" to "maintain an up-to-date Bugzilla system", 2015 is the perfect time to bring some of those Bugzilla improvements into the Testopia extension itself.

3) Improve my health

In about 5 months, I'm going to be a dad. I'd like to be an active part of her life.

Thursday, December 11, 2014

Testopia development is starting to pick up again, with consolidation efforts going smoothly so far.

Thursday, October 9, 2014

The framework upgrade for Testopia is officially on-hold.

Instead, I will be tackling a problem that plagues the development process of Testopia first, the code hierarchy itself. The biggest issue has been the lack of self-containment, making development inside of a development Bugzilla environment impossible without the use of symbolic links, which can cause unexpected code behavior.

Wednesday, October 8, 2014

After initial attempts to port the code straight to ext JS 5, I’ve determined that much of the codebase will require a rewrite in order to “play nice”. In fact, just bringing the code up one version to ext JS 4 would be a project on its own.

While I have no doubt in my mind that I will be able to bring Testopia’s codebase to ext JS 5, it may be a while away if I’m the only one working on it. Because of this, I will be working on both the upgrade and solving some of Testopia’s more annoying bugs simultaneously.

A Quick Update on Some Non-Game Projects

In case you don’t follow my Twitter, here is an update on some new projects I’ve taken on.


When I took on my current job, I knew that Bugzilla was going to be a part of it. I had tons of Perl experience before and some minor familiarity with Bugzilla, so I felt pretty confident going into this job two years ago. Then, I met Testopia.

Testopia is an extension to Bugzilla written by the person who used to have my position. Unlike most Bugzilla extensions, Testopia is more than just a simple additional functionality, it’s a full application. Problem is, the developer is unable to dedicate the time to keep this application moving forward, so it has a list of bugs and enhancements that have fallen to unknown status.

I hope to change that. While I wait to push my current work project live, I’ve been looking into upgrading the framework behind Testopia, extJS, which the project is currently running version 3 of. As of this month, version 5 has been released, making Google-fu the only way to find a working version of the framework when running the latest version of Testopia.

This project will be part of my normal 9-to-5, so I’m expecting to see this progress quite rapidly once all my research has completed.

REST-based Bugzilla App for Android

This one is more of a project I’m working on during my own free time, but slow periods at work may result in faster development (should still count if I’m supporting Bugzilla, right?). Bugzilla’s presence in the Play Store is sorely lacking, with many existing apps only working with older Bugzilla setups. Since Bugzilla is rapidly approaching towards favoring REST-based calls, I figured it’s time for a Bugzilla app that is future proof. I plan on initial releases to be free, with an ad-free premium version to come once the app has been fleshed out enough