Package com.atlassian.jira.webtests.ztests.workflow

Class TestDraftWorkflowSchemeMultipleProjectsMigration

java.lang.Object
com.atlassian.jira.functest.framework.BaseJiraFuncTest
com.atlassian.jira.webtests.ztests.workflow.AbstractTestWorkflowSchemeMigration
com.atlassian.jira.webtests.ztests.workflow.AbstractTestDraftWorkflowSchemeMigration
com.atlassian.jira.webtests.ztests.workflow.TestDraftWorkflowSchemeMultipleProjectsMigration
public class TestDraftWorkflowSchemeMultipleProjectsMigration extends AbstractTestDraftWorkflowSchemeMigration
Since:
v5.2

  • Constructor Details

    • TestDraftWorkflowSchemeMultipleProjectsMigration

      public TestDraftWorkflowSchemeMultipleProjectsMigration()

  • Method Details

    • testMigrateMultipleProjects

      public void testMigrateMultipleProjects()

    • testWorkflowMigrationHalfMigratedDataInTheFirstProject

      public void testWorkflowMigrationHalfMigratedDataInTheFirstProject()
      Tests workflow migration with previously failed migration.

      Imports a project which is still associated with its 'old' workflow scheme but issues TST-1, TST-2, TST-5 and TST-10 have been migrated to new workflows in the new workflow scheme

      This test migrates the issues again.

    • testWorkflowMigrationWithUnupdatedIssueInTheFirstProject

      public void testWorkflowMigrationWithUnupdatedIssueInTheFirstProject()
      Tests workflow migration with previously failed migtaion.

      Restore data where a workflow migration migrates issues TST-1, TST-2, TST-5 and TST-10 then creates a new wf entry for TST-4, marks an existing wf entry as killed, creates a new current step, removes the old one, and then dies. So we have a project which is still associated with its 'old' workflow scheme But some issues have been migrated to workflows in the new workflow scheme

      This test migrates the issues again.

    • testWorkflowMigrationWithUnupdatedWorkflowSchemeInTheFirstProject

      public void testWorkflowMigrationWithUnupdatedWorkflowSchemeInTheFirstProject()
      Tests workflow migration with previously failed migration.

      Restores data where a workflow migration dies after migrating all issues but still leaving behind the association to the old workflow scheme So we have a project which is still associated with its 'old' workflow scheme But all issues have been migrated to workflows in the new workflow scheme

      This test migrates the issues again.

    • testWorkflowMigrationHalfMigratedDataNewDestinationInTheFirstProject

      public void testWorkflowMigrationHalfMigratedDataNewDestinationInTheFirstProject() throws SAXException
      A general workflow migration test that tests quite a few cases. The test begins with imported data containing issues in Test project and Homosapien project and then migrates issues in Homosapien project from Homosapien Source Scheme workflow scheme to Homosapien Source Scheme draft. The Homosapien Source Scheme and its draft use different workflows for different issue types. Some issues in the Homosapien project are also 'broken' due to a previously failed workflow migration.

      The state of issues in the Homospaien project and where they are being migrated is discussed below:

      Bugs
      Some of the Bugs have been migrated from Homosapien Source 1 workflow to Homospien Destination Failure workflow. The migration failed before completion. When project workflow migration failed it left some issues using Homospien Destination Failure and some issues using the old (Homosapien Source 1) workflow. The data is in the state such that the issues that are using the Homospien Destination Failure workflow are in statuses that do not exist in the Homosapien Source 1 workflow. These statuses are:
      • In Progress
      • Closed
      • Custom Status 4

      Bugs will be migrated to a completely new workflow - Homospien Destination. That is, not the same workflow to which migration failed (Homospien Destination Failure).

      Improvements
      Improvements are being migrated from Homosapien Source 2 to the default jira workflow.

      New Features
      New Features are already using Homospien Destination workflow, so they should not be migrated at all.

      Tasks
      The source workflow for the Task is 'Homospien Destination' so normally we would not need to do any migration (as the destination workflow is also Homospien Destination. However, the previously failed migration has moved some of the Tasks to the Homospien Destination Failure workflow. These issues need to be moved (back) to the 'Homospien Destination' workflow. Hence we will need to get mapping for statuses:
      • In Progress
      • Closed

      which exist in Homospien Destination Failure workflow, but do not exist in Homospien Destination workflow.

      Sub-Tasks
      Sub-Tasks are using the Homosapien Source 1 workflow and are being migrated to the Homospien Destination workflow. There are no broken Sub-Tasks.

      Custom Issue Type
      Issues of Custom Issue Type are moving between Homosapien Custom Issue Type Source workflow and Homosapien Custom Issue Type Destination. All the statuses in Custom Issue Type Source workflow are in Homosapien Custom Issue Type Destination as well, so no status mapping should appear for Custom Issue Type issues

      The test also ensures that while migrating issues for the Homosapien project, the issues in Test project were not touched.

      Throws:
      SAXException

    • testIssueVerifierErrorInOneProject

      public void testIssueVerifierErrorInOneProject()
      Ensure the issue verifier detects problems before issues are migrated through workflow

    • testIssueVerifierErrorInBothProjects

      public void testIssueVerifierErrorInBothProjects()
      Ensure the issue verifier detects problems before issues are migrated through workflow

    • testMigrateMultipleProjectsIfNewProjectIsAssociatedWithTheScheme

      public void testMigrateMultipleProjectsIfNewProjectIsAssociatedWithTheScheme()

    • testMultiAdminTaskProgressFlowMultipleProjects

      public void testMultiAdminTaskProgressFlowMultipleProjects()
      Tests that 2 users can look at the same task and get their proper view of it, eg the starter can acknowledge and the other person cant

    • testMultiAdminTaskProgressFlowMultipleProjectsGoToSecondProject

      public void testMultiAdminTaskProgressFlowMultipleProjectsGoToSecondProject()