Implementation Guide: Test Plan

Sample test plan:

Sample plan to validate ignore/unignore/replace/cleanup:

Download this zip file containing all the referenced SQL scripts in these steps.

Step 0:

• Put “create_cms_content_ratings.sql” in your sql_direct directory and run packager.
• This will create a new table called “CMS_CONTENT_RATINGS”.

Step 1:

• Test for IGNORE use case –  Abandoning and Restoring a Changeset: ignore and unignore 
• Put “create_cms_content_ratings-ignore.sql” in your sql_direct directory and run packager again.
• This will essentially do nothing in your REF environment.
• Deploy changes to your DEV environment.
• Observe that table “CMS_CONTENT_RATINGS” does not get deployed there (because it is ignored).

Step 2:

• Test for UNIGNORE use case – Abandoning and Restoring a Changeset: ignore and unignore
• Put “create_cms_content_ratings-unignore.sql” in your sql_direct directory and run packager again.
• This will do nothing new to your REF environment
• Deploy changes to your DEV environment.
• Observer that that “CMS_CONTENT_RATINGS” is now deployed to DEV (because it is no longer ignored).

Step 3:

• Test for CLEANUP use case – Cleaning Up Deployed Changesets: cleanup 
• Put “create_cms_content_ratings-cleanup.sql” in your sql_direct directory and run packager again.
• This will remove the table “CMS_CONTENT_RATINGS” from your REF environment
• Deploy changes to your DEV environment.
• Observe that the table “CMS_CONTENT_RATINGS” is dropped from DEV.

Step 4:

• Test for REPLACE use case – Replacing Deployed Changesets: replace 
• Put “create_cms_content_ratings-replace.sql” in your sql_direct directory and run packager again.
• This will replace the table “CMS_CONTENT_RATINGS” in your REF environment  with “CMS_CONTENT_RATINGS_222” table
• Deploy changes to your DEV environment.
• Observe that the table “CMS_CONTENT_RATINGS” is replaced with “CMS_CONTENT_RATINGS_222” table