OK, so for the benefit if the three of you Testopia users that are left, I thought I would let you know I am wrapping up the project at work that has eaten all my waking hours in the coming weeks, and the focus is going to shift back towards Bugzilla/Testopia for a while. That means I have a lot of catching up to do. Especially given the announcement of Bugzilla 3.4 RC 1 right around the corner.
Also, it seems that Ext 3.0 is out. Just in time to fix a new batch of browser bugs (I hope). It appears that this version is going to have a lot of spiffy new features. Of course, I am not sure how to reconcile the continuing license issuse. No word on whether the existing FLOSS exception will carry over.
I have a slew of new ideas on top of the existing enhancements already logged. There is going to be a lot of work in the coming weeks.
Oh, and for those that use MediaWiki, you might want to check this out.
Stay tuned...
Wednesday, May 20, 2009
Tuesday, April 14, 2009
Hiatus
I have recently been assigned to a new project at work. This has limited the amount of time I am able to spend on Testopia and Bugzilla work while on the job. As I am also working on a masters degree part time, this limits my involvement outside of work. I have been keeping up with help requests and the like but have to take a hiatus on new development and bug fixes (unless those bugs impact our own installation) for a while. I continue to keep tabs on the incoming bugs and hope to have time soon to prioritize them. I also don't want to get too far behind the Bugzilla 3.4 branch so as to have the next version of Testopia ready in time for that release. In the meantime, I do have time to do reviews on patches and I welcome any and all who wish to tackle outstanding bugs or enhancements.
So in case you were wondering... I'm not dead yet.
I think I'll go for a walk.
So in case you were wondering... I'm not dead yet.
I think I'll go for a walk.
Monday, February 02, 2009
Testopia 2.2 is Here... Really... sort of...
Testopia 2.2 is out.
However, there still seem to be some lingering issues with upgrading from earlier versions. Specifically when it attempts to add foreign keys, you may get an error that looks something like this:
If you see this, it means (due to my earlier stupidity), that you will need to alter the columns referenced to remove the UNSIGNED attribute. This is most easily done using a nice GUI tool such as Mysql Query Browser where you can simply right click on a table, choose edit, and uncheck the box labeled UNSIGNED then click apply and then execute. However, you can also do it from the regular command line client with a command like:
Care should be taken to ensure that the column in question really is an INTEGER type (it may be SMALLINT for example) and if it is already an auto_increment column, you will need to add AUTO_INCREMENT at the end. It is best to do a describe table on both tables before hand to ensure the column types and which are key fields. Oh, and you did back up your database first right?
You may have to repeat this process on a handful of columns. I am working on a script that will (hopefully) clean all these up, but in the mean time, this is how to work these out manually if you are so inclined.
This is on Mysql. I am not sure how do it in Postgres or if this is even an issue there.
However, there still seem to be some lingering issues with upgrading from earlier versions. Specifically when it attempts to add foreign keys, you may get an error that looks something like this:
Adding foreign key: test_case_activity.case_id -> test_cases.case_id...
DBD::mysql::db do failed: Can't create table './bugs_bugzilla/#sql-965_5bde2.frm' (errno: 150)
[for Statement "ALTER TABLE test_case_activity ADD
CONSTRAINT fk_test_case_activity_case_id_test_cases_case_id FOREIGN KEY (case_id)
REFERENCES test_cases(case_id)
ON UPDATE CASCADE ON DELETE CASCADE"] at Bugzilla/DB.pm line 502
If you see this, it means (due to my earlier stupidity), that you will need to alter the columns referenced to remove the UNSIGNED attribute. This is most easily done using a nice GUI tool such as Mysql Query Browser where you can simply right click on a table, choose edit, and uncheck the box labeled UNSIGNED then click apply and then execute. However, you can also do it from the regular command line client with a command like:
ALTER TABLE `>table<`
MODIFY COLUMN `>column<` [INTEGER|SMALLINT|TINYINT] NOT NULL [AUTO_INCREMENT];
Care should be taken to ensure that the column in question really is an INTEGER type (it may be SMALLINT for example) and if it is already an auto_increment column, you will need to add AUTO_INCREMENT at the end. It is best to do a describe table on both tables before hand to ensure the column types and which are key fields. Oh, and you did back up your database first right?
You may have to repeat this process on a handful of columns. I am working on a script that will (hopefully) clean all these up, but in the mean time, this is how to work these out manually if you are so inclined.
This is on Mysql. I am not sure how do it in Postgres or if this is even an issue there.
Friday, December 19, 2008
A Tentative Step Forward
OK, so there is now an official BETA of Testopia 2.2 available, and for the fist time, I am trying to support multiple branches of development. 2.2 will support both Bugzilla 3.2 and 3.0.x.
Be sure to download the correct package for your installation!
You can get it from the project home page at http://www.mozilla.org/projects/testopia/ or from FTP
For the most part, upgrading should be the same as usual: unpatch, untar, re-patch, checksetup.
If you are upgrading Bugzilla at the same time, be sure to reverse the patch first.
So far this seems to work for Mysql with Firefox on Linux without mod_perl (my standard development system). I would love it if anyone wants to help test on other environments as I have limited time for testing these days.
I should stress that you should backup your database before attempting the upgrade. It has not been tested on a production system yet.
As usual Comments and questions should be posted to support-webtools@lists.mozilla.org
Happy Holidays
Be sure to download the correct package for your installation!
You can get it from the project home page at http://www.mozilla.org/projects/testopia/ or from FTP
For the most part, upgrading should be the same as usual: unpatch, untar, re-patch, checksetup.
If you are upgrading Bugzilla at the same time, be sure to reverse the patch first.
So far this seems to work for Mysql with Firefox on Linux without mod_perl (my standard development system). I would love it if anyone wants to help test on other environments as I have limited time for testing these days.
I should stress that you should backup your database before attempting the upgrade. It has not been tested on a production system yet.
As usual Comments and questions should be posted to support-webtools@lists.mozilla.org
Happy Holidays
Wednesday, December 03, 2008
Danger Will Robinson!!!
Bugzilla 3.2 is finally here. Hooray! :)
I reiterate again now that Bugzilla 3.2 is finally released that Testopia is not yet compatible with the new version. In fact...
UPGRADING BUGZILLA WITH TESTOPIA WILL CAUSE IRREPARABLE DAMAGE TO YOUR DATA!!!
Work is progressing on the upgrades and I will post further information as it comes available. Anyone wishing to help out in this regard is welcome to check out the tip from CVS, although it is not currently production ready.
I reiterate again now that Bugzilla 3.2 is finally released that Testopia is not yet compatible with the new version. In fact...
UPGRADING BUGZILLA WITH TESTOPIA WILL CAUSE IRREPARABLE DAMAGE TO YOUR DATA!!!
Work is progressing on the upgrades and I will post further information as it comes available. Anyone wishing to help out in this regard is welcome to check out the tip from CVS, although it is not currently production ready.
Monday, October 27, 2008
Vacation over, Back To Work.
Sorry for the long silence. I just got back from a much needed 2 weeks vacation in southern California. The kids had a blast at Disneyland and my wife got to pet penguins (a life long dream of hers) at Sea World.
Aside from having to reacclimatize to the 50 degree temperature difference, and digging myself out of two weeks worth of email, I am raring to go.
I am working out some issues with the Bugzilla devs dealing with database upgrades and foreign keys in Bugzilla 3.2 as well as ensuring that we have the necessary hooks set up. Otherwise the move to 3.2 is going very smoothly. Watch for the announcements for Bugzilla 3.2 and with luck, Testopia will be ready by then.
Aside from having to reacclimatize to the 50 degree temperature difference, and digging myself out of two weeks worth of email, I am raring to go.
I am working out some issues with the Bugzilla devs dealing with database upgrades and foreign keys in Bugzilla 3.2 as well as ensuring that we have the necessary hooks set up. Otherwise the move to 3.2 is going very smoothly. Watch for the announcements for Bugzilla 3.2 and with luck, Testopia will be ready by then.
Friday, September 12, 2008
Branching
Yesterday I branched for the Bugzilla 3.2 development. Moving forward, the tip will slowly be converting to the Bugzilla 3.2 codebase while the branch will stick to 3.0.x code.
This is an experiment for me to see if I, in all my ADHD glory, can manage to keep two active branches of development going simultaneously. For those of you interested, the TESTOPIA_2-1_BRANCH is the branch name in CVS.
Right now my thinking is that this will be kept up to date for Bugzilla 3.0.x primarily for bug fixes while new development and new features will stay on the tip. I guess it will depend on how much has to change between Bugzilla 3.0 and 3.2 in the areas where Testopia hooks or patches in. Where a clean patch can be applied, it won't hurt to have new features on both.
This is an experiment for me to see if I, in all my ADHD glory, can manage to keep two active branches of development going simultaneously. For those of you interested, the TESTOPIA_2-1_BRANCH is the branch name in CVS.
Right now my thinking is that this will be kept up to date for Bugzilla 3.0.x primarily for bug fixes while new development and new features will stay on the tip. I guess it will depend on how much has to change between Bugzilla 3.0 and 3.2 in the areas where Testopia hooks or patches in. Where a clean patch can be applied, it won't hurt to have new features on both.
Subscribe to:
Posts (Atom)
