sub parse { my ( $self, $xml, $product, $plans ) = @_; $debug = $self->debug;
# If the XML::Validator::Schema module is missing, we won't be able to parse # the XML file. So there is no need to go further. eval("require XML::Validator::Schema"); if ($@) { print "Failed to load, because : $@" return; }
/* after upgrading to TT 2.3, to make schema look like a clean install: purely cosmetic thou, everything works without doing this:-) PS: require that schema is already upgraded/converted to UTF-8! */
ALTER TABLE `test_case_categories` ADD PRIMARY KEY (`category_id`), DROP INDEX `category_id`; ALTER TABLE `test_case_categories` MODIFY COLUMN `category_id` SMALLINT(6) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_attachments` MODIFY COLUMN `attachment_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_builds` MODIFY COLUMN `build_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_case_run_status` MODIFY COLUMN `description` TEXT CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL; ALTER TABLE `test_case_runs` MODIFY COLUMN `case_run_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_case_runs` MODIFY COLUMN `priority_id` smallint(6) DEFAULT NULL; ALTER TABLE `test_case_status` MODIFY COLUMN `description` TEXT CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL; ALTER TABLE `test_cases` MODIFY COLUMN `case_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_cases` MODIFY COLUMN `isautomated` tinyint(4) NOT NULL DEFAULT '0'; ALTER TABLE `test_environment_category` MODIFY COLUMN `env_category_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_environment_element` MODIFY COLUMN `element_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_environments` MODIFY COLUMN `environment_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_events` ADD PRIMARY KEY (`eventid`), DROP INDEX `eventid`; ALTER TABLE `test_fielddefs` MODIFY COLUMN `fieldid` smallint(6) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_fielddefs` ADD PRIMARY KEY (`fieldid`), DROP INDEX `fieldid`; ALTER TABLE `test_plan_types` DROP INDEX `type_id`; ALTER TABLE `test_plans` MODIFY COLUMN `plan_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_plans` MODIFY COLUMN `isactive` tinyint(4) NOT NULL DEFAULT '1'; ALTER TABLE `test_relationships` ADD PRIMARY KEY (`relationship_id`), DROP INDEX `relationship_id`; ALTER TABLE `test_runs` MODIFY COLUMN `run_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_runs` DROP FOREIGN KEY `fk_test_runs_default_tester_id_profiles_userid`; ALTER TABLE `test_tags` MODIFY COLUMN `tag_id` int(11) NOT NULL AUTO_INCREMENT; ALTER TABLE `test_tags` ADD PRIMARY KEY (`tag_id`), DROP INDEX `tag_id`;
"Are you saying that XML::Validator::Schema causes mod_perl to break? How so? I have not seen this issue."
If you have the XML::Validator::Schema module, no problem, if not (if I remember correctly), checksetup.pl will crash/complain. XML::Validator::Schema is stated as optional, so it is not nice:-) AFAIK, all optional stuff must be eval'ed, so you can catch and handle the exception, if missing.
To reproduce, try to remove the XML::Validator::Schema module.
I have been using Bugzilla since the past 4 years and testopia since years. Have also been involved in the deployment and upgrade of Testopia and Bugzilla in my organisation.
I think Both these tools are absolutely great, considering they are open source, the only problem i think is the lack of documentation. I have been stuck many times and got lot of help from the Forums for the same.
Have just now upgraded Testopia from 2.2 to 2.3 but now i am not able to import testcases...
I made the mistake of moving my BugZilla to version 3.6 with the blind assumption that tesopia would run on it. So much for assuming... When do you plan on releasing a version compatible with BugZilla 3.6? I await it anxiously.
Currently I am involved in two mozilla projects: Bugzilla and Testopia.
I am not a software tester. In fact I don't really consider myself much of a software developer. I am more of what you might call and integrator. Still, that leaves the door open for a lot of software related things, including development and testing. As it so happens, I fell into these projects for the same reason many people get involved: the boss told me to.
I hang out in the mozwebtools, qa-bugzilla, and testopia channels on IRC (irc.mozilla.org).
13 comments:
mod_perl problem:
XML::Validator::Schema is OPTIONAL, but doesn't work with mod_perl:
bugzilla\extensions\testopia\lib\Testopia\Importer.pm
Change:
#use XML::Validator::Schema;
sub parse {
my ( $self, $xml, $product, $plans ) = @_;
$debug = $self->debug;
# If the XML::Validator::Schema module is missing, we won't be able to parse
# the XML file. So there is no need to go further.
eval("require XML::Validator::Schema");
if ($@) {
print "Failed to load, because : $@"
return;
}
This was my fix for the unsigned columns, for anyone upgrading:
/* do this before running checksetup, TT 2.2 BZ 3.2 */
/*unsigned cols problem*/
ALTER TABLE `test_tags` MODIFY COLUMN `tag_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_run_tags` MODIFY COLUMN `tag_id` INT(10) NOT NULL DEFAULT 0;
ALTER TABLE `test_run_activity` MODIFY COLUMN `fieldid` SMALLINT(5) NOT NULL DEFAULT 0;
ALTER TABLE `test_runs` MODIFY COLUMN `run_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_relationships` MODIFY COLUMN `relationship_id` TINYINT(3) NOT NULL DEFAULT 0;
ALTER TABLE `test_plan_tags` MODIFY COLUMN `tag_id` INT(10) NOT NULL DEFAULT 0;
ALTER TABLE `test_plan_activity` MODIFY COLUMN `fieldid` SMALLINT(5) NOT NULL DEFAULT 0;
ALTER TABLE `test_plans` MODIFY COLUMN `plan_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_fielddefs` MODIFY COLUMN `fieldid` SMALLINT(5) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_events` MODIFY COLUMN `eventid` TINYINT(3) NOT NULL DEFAULT 0;
ALTER TABLE `test_environment_element` MODIFY COLUMN `element_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_environment_category` MODIFY COLUMN `env_category_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_environments` MODIFY COLUMN `environment_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_email_settings` MODIFY COLUMN `eventid` TINYINT(3) NOT NULL DEFAULT 0, MODIFY COLUMN `relationship_id` TINYINT(3) NOT NULL DEFAULT 0;
ALTER TABLE `test_case_tags` MODIFY COLUMN `tag_id` INT(10) NOT NULL DEFAULT 0;
ALTER TABLE `test_case_runs` MODIFY COLUMN `case_run_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_case_categories` MODIFY COLUMN `category_id` SMALLINT(5) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_case_activity` MODIFY COLUMN `fieldid` SMALLINT(5) NOT NULL DEFAULT 0;
ALTER TABLE `test_cases` MODIFY COLUMN `case_id` INT(10) NOT NULL AUTO_INCREMENT, MODIFY COLUMN `category_id` SMALLINT(5) NOT NULL DEFAULT 0;
ALTER TABLE `test_attachments` MODIFY COLUMN `attachment_id` INT(10) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_builds` MODIFY COLUMN `build_id` INT(10) NOT NULL AUTO_INCREMENT;
/* after upgrading to TT 2.3, to make schema look like a clean install: purely cosmetic thou, everything works without doing this:-) PS: require that schema is already upgraded/converted to UTF-8! */
ALTER TABLE `test_case_categories` ADD PRIMARY KEY (`category_id`), DROP INDEX `category_id`;
ALTER TABLE `test_case_categories` MODIFY COLUMN `category_id` SMALLINT(6) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_attachments` MODIFY COLUMN `attachment_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_builds` MODIFY COLUMN `build_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_case_run_status` MODIFY COLUMN `description` TEXT CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL;
ALTER TABLE `test_case_runs` MODIFY COLUMN `case_run_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_case_runs` MODIFY COLUMN `priority_id` smallint(6) DEFAULT NULL;
ALTER TABLE `test_case_status` MODIFY COLUMN `description` TEXT CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL;
ALTER TABLE `test_cases` MODIFY COLUMN `case_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_cases` MODIFY COLUMN `isautomated` tinyint(4) NOT NULL DEFAULT '0';
ALTER TABLE `test_environment_category` MODIFY COLUMN `env_category_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_environment_element` MODIFY COLUMN `element_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_environments` MODIFY COLUMN `environment_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_events` ADD PRIMARY KEY (`eventid`), DROP INDEX `eventid`;
ALTER TABLE `test_fielddefs` MODIFY COLUMN `fieldid` smallint(6) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_fielddefs` ADD PRIMARY KEY (`fieldid`), DROP INDEX `fieldid`;
ALTER TABLE `test_plan_types` DROP INDEX `type_id`;
ALTER TABLE `test_plans` MODIFY COLUMN `plan_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_plans` MODIFY COLUMN `isactive` tinyint(4) NOT NULL DEFAULT '1';
ALTER TABLE `test_relationships` ADD PRIMARY KEY (`relationship_id`), DROP INDEX `relationship_id`;
ALTER TABLE `test_runs` MODIFY COLUMN `run_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_runs` DROP FOREIGN KEY `fk_test_runs_default_tester_id_profiles_userid`;
ALTER TABLE `test_tags` MODIFY COLUMN `tag_id` int(11) NOT NULL AUTO_INCREMENT;
ALTER TABLE `test_tags` ADD PRIMARY KEY (`tag_id`), DROP INDEX `tag_id`;
Are you saying that XML::Validator::Schema causes mod_perl to break? How so? I have not seen this issue.
"Are you saying that XML::Validator::Schema causes mod_perl to break? How so? I have not seen this issue."
If you have the XML::Validator::Schema module, no problem, if not (if I remember correctly), checksetup.pl will crash/complain. XML::Validator::Schema is stated as optional, so it is not nice:-) AFAIK, all optional stuff must be eval'ed, so you can catch and handle the exception, if missing.
To reproduce, try to remove the XML::Validator::Schema module.
OK, I see what you mean. Can you please log a bug with this?
Good dispatch and this enter helped me alot in my college assignement. Thanks you on your information.
Thanks into sharing. Like at all times, on the money and right on objective!
I have been using Bugzilla since the past 4 years and testopia since years. Have also been involved in the deployment and upgrade of Testopia and Bugzilla in my organisation.
I think Both these tools are absolutely great, considering they are open source, the only problem i think is the lack of documentation.
I have been stuck many times and got lot of help from the Forums for the same.
Have just now upgraded Testopia from 2.2 to 2.3 but now i am not able to import testcases...
How were you importing before? What kind of error are you seeing? Can you be more specific? You should post these details to the support list.
I am trying to find screen shots or a demo of Testopia, am I missing something?
I made the mistake of moving my BugZilla to version 3.6 with the blind assumption that tesopia would run on it. So much for assuming... When do you plan on releasing a version compatible with BugZilla 3.6? I await it anxiously.
Thanks,
Bill
Quite interesting to be seen about this...
Lowest Unique Bid
Online Penny Auctions
Post a Comment