Post-Merge Testing of Upstream Releases v4.0.0, v4.0.1, and v4.0.2

[aaronskiba]

This issue has been created for the purpose of documenting manual tests performed against the merges of upstream releases v4.0.0, v4.0.1, and v4.0.2.

[aaronskiba]

v4.0.0

Changes Outlined in v4.0.0 Release

• "Updated the PDF coversheet to include all Contributors"

  • TEST
    1. Create a plan
    2. Add 2 contributors
       
    3. Download the plan and ensure the two contributors and their correct roles are displayed
       
  • RESULTS
    1. The contributors and their roles are visible on the downloaded plan.
    2. HOWEVER, there are duplicate occurrences of them within the downloaded plan. (TODO: Check further upstream releases to see if this bug has been addressed).
       NOTE:
    3. The duplicate occurrences don't occur with the release v4.0.0 version of the upstream app.
       
  • UPDATE
    1. There was duplicate code in app/views/shared/export/_plan_coversheet.erb. Removing the duplicate code removed the duplicate listings of contributors.
       

• "Fixed an issue that was causing the link to organizational guidance to repeat"

  • TEST (I hope I am testing the correct "link to organizational guidance")

    1. As an admin, create and publish a guidance for the organisation. Check all themes.
       
    2. Create a new template for the organisation. Add a phase, a question, and a theme for the question.
       
    3. Publish the template
       
    4. Create a plan. Select the organisation and the newly published template.
       
    5. Ensure there are no repeat links to organizational guidance.
       

  • RESULTS

    1. Unfortunately, there is a repeat link to the Portage Network organisation.

  • NOTE

    1. This problem DOES NOT seem to exist prior to merge of v4.0.0 release
    2. In GET /plans/show (app/controllers/plans_controller.rb) @important_orgs seems to include duplicate entries.
    3. This issue also seems to exist on the upstream app for release v4.0.0 ( and the bug persists for release v4.1.0)
       

• "Fixed an issue that was impacting API v0 and preventing the batch assignment of users to departments"

  • TEST

  • 1. Assign multiple users to a department and verify the assignment.
       
       
  • 2. Unassign these same users from the department and verify the unassignment.
       
       (The emails now belong to the followingnull department):
       

  • RESULTS

• "Fixed an issue that was preventing admins from performing a search on the Templates page Template Search issue DMPRoadmap/roadmap#3217"

  • TEST

    1. As an admin, navigate to templates.
    2. Type 'test' in the search bar and inspect the returned results
       

  • RESULTS

    1. Templates search appears to be working.

• Removed case sensitivity from the validation rules for Org and Department names.

  • TEST

  • RESULTS

• "Fixed issues with API v1"

  • TEST

  • RESULTS

• "Fixed an issue that was causing plans that were based off of templates with conditional questions to disappear when the user triggered the condition Conditional questions causing plans to disapear  DMPRoadmap/roadmap#3163"

  • TEST

  • RESULTS

• "Fixed an issue that was causing plans to not appear in the publicly visible if 100% of their questions had not been answered Org visibility plan will appear in the public DMPs only if filled 100% DMPRoadmap/roadmap#3086"

  • TEST

  • RESULTS

v4.0.1

Changes Outlined in v4.0.1 Release

v4.0.2

Changes Outlined in v4.0.2 Release