[WG: Sakai QA] Sakai Conversion testing

[Adam Hocek]

Hi Alan,

I have completed the conversion scripts for 2.7 having performed steps 1 & 
2.   So far there is one table (SAKAI_PERSON_T) that has a table size 
issue which I will send in a separate email.
Performing step 3 is something we were going to do next and shouldn't be a 
problem.  I'm not familiar with SQL Developer, but if it can simplify the 
comparison of the converted and clean instance of 2.7 beta database then 
that would make doing steps 4-7 a lot easier.  Performing step 3 by next 
week is not a problem, but with current schedules I would want to say that 
steps 4-7 can be completed by end of May or sooner. 

- Adam


Adam Hocek
Information Technology
Marist College
tel: 845-575-3948



From:
Alan Berg <qa.director.sakai at gmail.com>
To:
Matthew Jones <jonespm at umich.edu>, Adam Hocek <Adam.Hocek at marist.edu>
Cc:
Anthony Whyte <arwhyte at umich.edu>, Seth Theriault <slt at columbia.edu>, 
Sakai QA <sakai-qa at collab.sakaiproject.org>
Date:
04/29/2010 11:40 AM
Subject:
Re: Sakai Conversion testing



Hi Adam,

We are just about to move to RC (with the assumption that all blockers 
have been removed by then which is a good bet).
Matthew Jones has been kind enough to make a plan for testing the 
effectiveness of conversion scripts. Is it possible to do the same (or 
similar) for DB2 before 2.7 is released?

Alan

On Thu, Apr 29, 2010 at 5:36 PM, Matthew Jones <jonespm at umich.edu> wrote:
So just a followup from the call re: conversions.

We need to run the conversions before the move to RC. Either Anthony 
and/or myself will be able to do this next week. The verification will 
happen by:

(Conversion script verification)
1) Installing the latest 2.6 release (2.6.2) with auto.ddl=true. This 
needs to be done on both oracle and mysql. 
  - DB2 does not appear to have a complete conversion script and I don't 
have access to test this. DB2 will not hold up the RC.
2) Run the conversion script rollups: 
"sakai_2_7_0_oracle_conversion.sql" sakai_2_7_0_mysql_conversion.sql"
  - Note any errors (if any) that occur while running the script
3) Attempt to start up Sakai 2.7-beta with auto.ddl=false. Note any 
database error (if any) when starting up

(Table structure verification)
4) On the converted databases, run a tool to export the DDL of the tables, 
sequences.
  -  It seems like SQL Developer will work for this.
5) Start up the 2.7-beta instance with auto.ddl=true on an empty database
6) On the 2.7 database, run the same tool to export the DDL
7) Compare the resulting SQL files, noting any differences. If any are 
found these will need to be jira'd and added to the conversion script.

Followup: Ideally if there are any missing conversions found in any part 
of the process these steps will need to be repeated with the updated 
conversion script.

Additional details will follow.

Currently known missing conversion.

This should not be a blocker for RC, but I might elevate it's priority and 
consider it a 'need to be fixed' for the final 2.7.0 release. This will 
not be able to be written as a simple SQL conversion script and will need 
some code to process this, so might be 2-3 weeks to get around to fixing 
it)

http://jira.sakaiproject.org/browse/SAK-18406 (Create a migration script 
to get older announcement data updated with new implementation of 
assignment/announcement integration)



-- 
Alan

Alan Berg
Interim QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20100429/826ea7f9/attachment.html