Testing/Manual testing

From Mahara Wiki
Revision as of 10:54, 24 May 2018 by Stevens (talk | contribs) (Manual Test script scenarios for ?????? pages)

Jump to: navigation, search

This page will outline the manual testing of Mahara in sections as outlined in the Mahara user manual

Manual Testing Important Information

For manual testing it is assumed that a fresh install of Mahara has taken place and user sets "Password" and "email" for the initial login. It is also assumed that there is a fresh database with no data. Other themes will have to be set by the Site admin in the Site settings panel found here Admin menu > Configure site > Site options > Site settings


Manual Test script scenarios for Dashboard

Manual Test Scenario: User should see correct page styling
Login Block Ocean theme
Login Block Modern theme
Login Block Primary school theme
Login Block Raw theme
Given user is logged in
When user is on the "Mahara homepage"
Then user should see "Raw" theme colours






Manual Test Scenario: User can see help icon in the login block
Login Block Ocean theme
Login Block Modern theme
Login Block Primary school theme
Login Block Raw theme
Given user is not logged in
And the SIte theme is set to "Modern Theme"
When user is on the login page
Then user should see a help icon displayed in top right corner of login block






Manual Test Scenario: "Registration" links to "Registration" page


Login Block Ocean theme
Login Block Modern theme
Login Block Primary school theme
Login Block Raw theme
Given I am on homepage
When I follow "Register"
And I fill in the following:
| First name | Lightening |
| Last name | McQueen |
| Email address | fakeymcfakey@example.org |
| Registration reason | I will absolutely make this institution more amazing!! |
And I press "Send request"
Then I should see "You should receive an email shortly with a link that you can use to change the password for your account."
And email is recieved - this requires a manual inspection of email address to ensure email was sent and is correct
Manual Test Scenario: User clicks "Lost username / password" to receive an email to log into site
Reset Email Instructions
Given I am on homepage
When I follow "Lost username / password"
And I fill in "Email address or username" with "UserA"
And I press "Send request"
Then I should see "You should receive an email shortly with a link that you can use to change the password for your account."
And email is recieved - this requires a manual inspection of email address to ensure email was sent and is correct


Manual Test Scenario: Profile completion block is displayed correctly and functioning
Reset Email Instructions
Given the Profile completion is turned on (Admin menu > Site options > User settings > Show profile completion = Yes)
And Profile completions fields have been selected by Admin ( Admin menu > Institution > Profile completion - selected profile fields)
And user is logged in
When user is on "Dashboard" page
Then user should see a "Profile completion block" in the right hand column of the page
When user has completed the required fields of their profile pages
Then user should see the progress bar highlighted with a colour and a percentage of completed fields in the Profile completion block







Manual Test script scenarios for Profile pages

Manual Test Scenario: User should see correct page styling
Login Block Ocean theme
Login Block Modern theme
Login Block Primary school theme
Login Block Raw 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"
Manual Test Scenario: Multiple Email Functionality
Login Block Ocean theme
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.
Login Block Ocean theme
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



Manual Test script scenarios for Portfolio pages

Manual Test Scenario: User should see correct page styling
Login Block Ocean theme
Login Block Modern theme
Login Block Primary school theme
Login Block Raw 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"




Manual Test script scenarios for Content Files

Manual Test Scenario: User should see correct page styling
Files page 24-05-18-10-52-37.png


  1. Visual check
    1. Files page uses correct colour
    2. header elements displayed
    3. online users block displayed
    4. Quota block displayed
    5. footer is displayed and links functioning correctly




BUGS to test for Manually

Bug 1702198: All users with exception of root user has ctime set when they are first created
Original Bug: https://bugs.launchpad.net/mahara/+bug/1702198/comments/2

Environment to be tested: Master
Browser to be tested: Chrome

Create new admin user and Log into Database using the following commands

    sudo -u postgres psql                           - starts PSQL terminal
    \l                                              - lists databases 
    \c <db name>                                    - connect to database 
    Select ctime from usr where username='admin';   - returns date/time user was created 

Date should be date user was created


Bug 1726655: Mahara logo is cut off at the bottom in IE11.

Environment to be tested: Master
Browser to be tested: IE 11

Precondition: The institution 'Institution A' exists and the user is a admin in that institution.

Steps to reproduce: 1. Open IE 11 and enter the URL to the Mahara instance.
Expected result: Mahara logo should be displayed properly without any cut off.
2. Log in as ‘Institution admin’.
Expected result: Mahara logo should be displayed properly without any cut off.

3. Navigate to Administration menu > Institutions > Settings.
4. Click the ‘Settings’ button for ‘Institution A’.
5. Upload a logo and Click the ‘Submit’ button.
6. Log out and Log in back as ‘Institution admin’.
Expected result: Mahara logo should be displayed properly without any cut off.
7. Compare the Mahara logo with another browser and verify if the dimensions are aligned properly.
Expected result: Mahara logo should have the same dimensions as the other browser.


Bug 1726560: Add recaptcha field to contact us form when logged out

Environment to be tested: Master
Browser to be tested: Any browser

Precondition: 1. A user with 'Site admin' access exists.
2. 'reCAPTCHA site key' & 'reCAPTCHA secret key' are generated.
NOTE: You create the 'reCAPTCHA site key' & 'reCAPTCHA secret key' at https://www.google.com/recaptcha/admin
3. Normal user ‘User one’ exists.

Steps to reproduce: 1. Log in as 'Site admin'.
2. Navigate to Administration menu > Configure site > Site options > Security settings.
3. Switch 'reCAPTCHA on user registration/contact us forms' to 'Yes'.
4. Enter the 'reCAPTCHA site key' & 'reCAPTCHA secret key'.
5. Click the 'Update site options' button.
6. Log out as 'Site admin'.
7. Click the hyperlink 'Contact us', which is at the bottom of the page.
Expected result: A captcha field is displayed on the form. 8. Enter an email into the 'Email' field.
9. Enter the name 'Tester' into the 'Name' field.
10. Enter the text as 'This is a test message' into the 'Message' field.
11. Select the checkbox 'I'm not a robot'.
12. Click the 'Send message' button.
Expected result: The Mahara homepage is displayed with a message 'Your message has been sent'. 13. Log in as 'User one'.
14. Click the hyperlink 'Contact us', which is at the bottom of the page.
Expected result: The captcha field is not displayed on the form and the 'Email'and 'Name' fields are auto populated. 15. Enter the text as 'This is a test message' into the 'Message' field.
16. Click the 'Send message' button.
Expected result: The Mahara dashboard page is displayed with a message 'Your message has been sent'.


BUG 1772298 - Bug description: login help icon hidden on Modern theme

Environment to be tested: Master
Browser to be tested: Chrome

Summary: Help icon is missing when the site theme is set to Modern theme and the user is on the log in page.

1. site has Modern Theme set
2. User is on the login screen

Actual result: the help icon is hidden - if user clicks in the general area the help text is displayed

Expected result: help icon is displayed and is clickable to reveal help text.


Bug 1734557: Allow SAML plugin to have custom auth error message - like Xmlrpc

Environment to be tested: Master
Browser to be tested: Chrome

Precondition:

1. A user with 'Site admin' access exists.
2. ‘Institution A' exists.

Steps to reproduce:

1. Log in as ‘Site admin’.
2. Navigate to Administration menu > Institutions > Settings.
3. Click the ‘Settings’ button for ‘Institution A’.
4. Select ‘SAML’ from the ‘Authentication plugin’ drop-down menu.
5. Add ‘SAML’ meta data and make sure the 'Authentication login message' is set up with the text ‘This is an error message’.
6. Click the ‘Submit’ button.
7. Click the 'Save' button.
8. Set up a new user that has SAML as authentication method in that institution and make sure you set a remote username for them.
9. Log out as ‘Site admin’.
10. Now try to log in as ‘User one’ using the regular login fields and not the SSO button.

Expected result: ‘User one’ is not able to log in and the authentication login error message box is displayed: ‘This is an error message’.