[Testrunner-users] Current work

[Fuentetaja, E. <ed....@tt...>]

After releasing version 0.4.5 I'm currently working on facilitating a
migration path from version 0.3 (bugzilla 2.16) to 0.4.5 (bugzilla 2.17)

I got a patch working for version 2.16.3. But the biggest obstacle is
the that there are some changes in the bugzilla's db that affect Test
Runner:
- Table components: version 2.17 added a new column ID, and VALUE was
renamed to NAME
- Table products: almost the same: new column ID and PRODUCT renamed to
NAME

My idea is to run a sql patch on 2.16 that adds ID columns to both
tables. Type will be autoincrement, so even if Bugzilla 2.16 doesn't
know about those columns, they will be automatically populated for new
products. I think it's going to be safe.
I won't rename the other two columns, I want to minimize patching
Bugzilla's code. Rather than that, I'll detect the current version of
the DB and use one name or the other on the Test Runner queries.

I got a working version (modified code of 0.4.5 running on a Bugzilla
2.16.3) I just need to write some code to detect the version and change
the content of the couple of global variables that contain the name of
the columns, do more testing with both Bugzilla 2.16 and 2.17 and I'll
be ready to go.

Testing so far seems to be OK. I'm very excited because there are some
people using Bugzilla 2.16 and if I can provide them with the advantages
of Test Runner 0.4.5 is going to be great. And I'll only have one single
version to maintain.

	Ed