Testing Area/Manual regression testing

Manual regression testing

This page outlines the manual regression testing for Mahara releases (6 monthly; YY.04 and YY.10).

Automated (unit and Behat) and manual testing is performed during the release development period for each Launchpad/Gerrit item prior to its merge into the master branch (see Manual item testing in this page's parent page). Regression testing is then performed upon the release candidate prior to its actual go-live. This page contains an overview of the manual regression testing i.e. coverage of main functionality, such as email interaction, that is not being addressed by automated testing. It also provides a record of main screen presentations.

Manual Regression Testing Preconditions

For manual regression testing it is assumed that:

1. a fresh install of Mahara has taken place and "Password" and "email" are set for the initial Site admin login
2. there is a fresh database with no data
3. Mahara emails have been set to be delivered to an inbox the tester has access to (via config.php & see next point's 'Site settings')
4. the theme will be (re-)set by the Site admin in Admin menu > Configure site > Site options > Site settings
5. at least one account (named PersonA) other than the Site admin account is active (via manual individual account add or csv file account creation)
6. the default browser (used to take the actual result screen shots) is currently Chrome running on a Windows10 (virtual) machine
7. other test platforms include Win10-Edge and Win10-Firefox (OSx-Safari & Android-Chrome if time permits)
8. the latest stable browser versions are used.

Manual Regression Testing Scenarios

Expand

Manual test scenarios for LogIn and Logged Out (Homepage) pages

Expand

Homepage Scenario 1: Mahara "Homepage" (log in page) content and styling is correct.

Raw theme

Primary school theme

Default theme

Ocean theme

Modern theme

Maroon theme

Given PersonA has their browser open

When PersonA enters the correct URL for Mahara

Then PersonA should see the "Mahara homepage" content displayed in the correct theme colours and style.

Expand

Homepage Scenario 2: PersonA can successfully reset their Mahara password.

Reset Email Instructions

Given PersonA is on the "homepage"

When PersonA follows "Lost username / password"

And PersonA fills in "Email address or username" with "PersonA"

And PersonA presses "Send request"

Then PersonA should see "You should receive an email shortly with a link that you can use to change the password for your account."

And an email is received - manually inspect inbox to ensure email was sent and is correct.

When PersonA follows "Email confirmation link"

Then PersonaA fills in "New password" with ".3Kg@4!O"

And PersonaA fills in "Re-enter password" with ".3Kg@4!O"

And PersonA presses "Send request"

Then PersonA should see their Dashboard displayed

When PersonA follows "Log out"

Then PersonA should see the Mahara "homepage" displayed correctly

When PersonA fills in "Username" with "PersonA"

And PersonA fills in "Password" with ".3Kg@4!O"

And PersonA presses "Log in"

Then PersonA should see their Dashboard displayed

Expand

Homepage Scenario 3: Logged out person should see correct page content and styling

Raw theme

Primary school theme

File:Default theme - Dashboard - Mahara - 04 - 04 - 2018.png Default theme

Ocean theme

Modern theme

Given person has their browser open

When person enters the correct URL for Mahara

Then they should see the "Mahara homepage" content displayed in the correct theme colour and style.

Expand

Manual test scenarios for [default] Dashboard page

Expand

Dashboard Scenario 1: Site admin should see correct Dashboard page content and styling

Raw theme

Primary school theme

File:Default theme - Dashboard - Mahara - 04 - 04 - 2018.png Default theme

Ocean theme

Modern theme

Given Site admin has an active Mahara site administrator account

When they successfully complete the Mahara log in process

Then they should see correct page content and styling for the default site administrator Dashboard page.

Expand

Dashboard Scenario 2: PersonA (non-admin) should see correct Dashboard page content and styling

Raw theme

Primary school theme

File:Default theme - Dashboard - Mahara - 04 - 04 - 2018.png Default theme

Ocean theme

Modern theme

Given PersonA has an active non-administrative Mahara account

When they successfully complete the Mahara log in process

Then they should see correct page content and styling for the default Dashboard page.

Expand

Manual test scenarios for [default] Profile page

Expand

Profile scenario 1: PersonA should see correct page content and styling on their default Profile page.

File:Profile-About Me-Mahara-Raw.png Raw theme

Primary school theme

File:Profile-About Me-Mahara-Default.png Default theme

Modern theme

Ocean theme

1. Visual check
   1. Profile page uses correct colour "Raw"
   2. header elements displayed
   3. Static Profile Page title h1 displayed
   4. online users block displayed
   5. footer is displayed and links functioning correctly
2. Change page "Layout" functionality works
3. Change page "Skin" functionality works
4. Page edit functionality works Create edit and delete page blocks
5. Page links working Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"

Expand

Profile scenario 2: Multiple Email Functionality

Multiple Email

Scenario: Only one email address: There should not be a delete button as the only email address cannot be deleted.

Given user logged in

And has one email address

And is on the Profile > Contact information page

When user clicks the delete icon to right of email address

Then user should see message "You cannot remove your primary email address." displayed

And the email address will not be deleted

Scenario: One or more email addresses: The primary email does not have delete button. When the primary address is changed, it should receive the delete button and the now primary email address gets it removed.

Multiple Email Addresses

Given user logged in

And has more than one email address

And user has validated the email mail address

When user is on the Profile > Contact information page

And user has selected the second email address

And clicks the delete icon associated with the first email in the list

And then the first email in the list will be deleted

Expand

Manual test scenarios for Create pages

Expand

Create Pages and Collections scenario 1 : PersonA should see correct page content and styling on their default Create 'Pages and Collections' home page

Raw theme

Primary school theme

File:PortfolioOverviewDefault 18-05-18-14-29-30.png Default theme

Ocean theme

Modern theme

1. Visual check
   1. Profile page uses correct colour "Raw"
   2. header elements displayed
   3. Static Profile Page title h1 displayed
   4. online users block displayed
   5. footer is displayed and links functioning correctly
2. Change page "Layout" functionality works
3. Change page "Skin" functionality works
4. Page edit functionality works Create edit and delete page blocks
5. Page links working Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"

Expand

Create Files scenario 1: PersonA should see correct page content and styling on their default Create 'Files' home page

1. Visual check
   1. Profile page uses correct colour "Raw"
   2. header elements displayed
   3. Static Profile Page title h1 displayed
   4. online users block displayed
   5. footer is displayed and links functioning correctly
2. Change page "Layout" functionality works
3. Change page "Skin" functionality works
4. Page edit functionality works Create edit and delete page blocks
5. Page links working Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"

Expand

Create Files scenario 2: User "Quota" block updates as files are added

1. Confirm that when files are added the Quota block updates and the display bar is filled in accordingly.

Expand

Create Files scenario 3: Image files can be edited and rotated

Preconditions:

1. User has Image files loaded into Mahara
2. User has document files loaded into Mahara

Test Script:

1. User browse to Main menu > Content > Files
2. User edit an Image file by clicking the pencil icon to right of image file
3. Confirm there is an rotate icon to right of image in the Edit file section of the page
4. Click the rotate icon
5. Confirm that the image preview rotates 1/4 turn to the right each time the rotate icon is clicked

Expand

Create Files scenario 3: User should be able to drag and drop files to a page for upload

Preconditions:

1. User has Image files on their local machine
2. User has document files on their local machine

Test Script:

1. User browse to Main menu > Content > Files
2. Confirm that there is a "Drop files here to upload" section on the page
3. User open the file browser for their local machine
4. User browse to a file to upload to Mahara
5. using the cursor, hover over the desired file
6. click and hold while draging the file to the dark grey Drag N Drop section of the Page
7. release the click
8. Confirm that the file is uploaded and a message is displayed as follows :Upload of <file name> complete
9. Repeat the above steps for different file types that Mahara will accept (ie.. image file types jpg png, document file types docx, PDF)

Expand

Create Skins scenario 1 : PersonA should see correct page content and styling on their default Create 'Skins' home page

Raw theme

Primary school theme

File:PortfolioOverviewDefault 18-05-18-14-29-30.png Default theme

Ocean theme

Modern theme

1. Visual check
   1. Profile page uses correct colour "Raw"
   2. header elements displayed
   3. Static Profile Page title h1 displayed
   4. online users block displayed
   5. footer is displayed and links functioning correctly
2. Change page "Layout" functionality works
3. Change page "Skin" functionality works
4. Page edit functionality works Create edit and delete page blocks
5. Page links working Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"

Expand

Manual test scenarios for 'Manage'

Expand

Upload Leap2A file scenario 1: User can upload an Leap2A file

Leap2a import page

Leap2A imported data

Preconditions:

1. User has a Leap2A zip file from a previous export of all of "Admin User" data.
2. user has unzipped the file which should include
   1. files folder containing image files, document files that have been used on users's profile/portfolio
   2. leap2a.xml file

Test Script:

1. user (someone other than admin) log in
2. Browse to Main menu > Portfolio > Import
3. Click the choose a file and upload the "leap2a.xml" file of the Admin User profile
4. Click the import button
5. Confirm you see the all the data that will be imported
6. Select the information you want to ignore, append, replace or add new
7. click the "Import" button
8. Note that you will have to upload the files into the folders
9. view the areas that you have added ie Portfolio pages
10. confirm that the new pages are displayed with the content on the pages