Actions

Testing Area/Manual regression testing: Difference between revisions

From Mahara Wiki

< Testing Area
mNo edit summary
Line 384: Line 384:
<div class="toccolours mw-collapsible mw-collapsed" style="background:#daecd6">
<div class="toccolours mw-collapsible mw-collapsed" style="background:#daecd6">


==BUGS to test for Manually==
<div class="mw-collapsible-content">
<span style="background:#e3baba">'''Bug 1702198:''' All users with exception of root user has ctime set when they are first created </span> <br/>
'''Original Bug:''' https://bugs.launchpad.net/mahara/+bug/1702198/comments/2
'''Environment to be tested:''' Master<br/>
'''Browser to be tested:''' Chrome <br/>
Create new admin user and Log into Database using the following commands
<pre>
    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
</pre>
Date should be date user was created
-----
<span style="background:#e3baba">'''Bug 1726655:''' Mahara logo is cut off at the bottom in IE11.</span>
'''Environment to be tested:''' Master<br/>
'''Browser to be tested:''' IE 11<br/>
'''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.<br/>
'''Expected result:''' Mahara logo should be displayed properly without any cut off.<br/>
2. Log in as ‘Institution admin’.<br/>
'''Expected result:''' Mahara logo should be displayed properly without any cut off.<br/>
3. Navigate to Administration menu > Institutions > Settings.<br/>
4. Click the ‘Settings’ button for ‘Institution A’.<br/>
5. Upload a logo and Click the ‘Submit’ button.<br/>
6. Log out and Log in back as ‘Institution admin’.<br/>
'''Expected result:''' Mahara logo should be displayed properly without any cut off.<br/>
7. Compare the Mahara logo with another browser and verify if the dimensions are aligned properly.<br/>
'''Expected result:''' Mahara logo should have the same dimensions as the other browser.
-----
<span style="background:#e3baba">'''Bug 1726560:''' Add recaptcha field to contact us form when logged out</span><br/>
'''Environment to be tested:''' Master<br/>
'''Browser to be tested:''' Any browser<br/>
'''Precondition:'''
1. A user with 'Site admin' access exists.<br/>
2. 'reCAPTCHA site key' & 'reCAPTCHA secret key' are generated.<br/>
'''NOTE:''' You create the 'reCAPTCHA site key' & 'reCAPTCHA secret key' at https://www.google.com/recaptcha/admin <br/>
3. Normal user ‘User one’ exists.
'''Steps to reproduce:'''
1. Log in as 'Site admin'.<br/>
2. Navigate to Administration menu > Configure site > Site options > Security settings.<br/>
3. Switch 'reCAPTCHA on user registration/contact us forms' to 'Yes'.<br/>
4. Enter the 'reCAPTCHA site key' & 'reCAPTCHA secret key'.<br/>
5. Click the 'Update site options' button.<br/>
6. Log out as 'Site admin'.<br/>
7. Click the hyperlink 'Contact us', which is at the bottom of the page.<br/>
'''Expected result:''' A captcha field is displayed on the form.
8. Enter an email into the 'Email' field.<br/>
9. Enter the name 'Tester' into the 'Name' field.<br/>
10. Enter the text as 'This is a test message' into the 'Message' field.<br/>
11. Select the checkbox 'I'm not a robot'.<br/>
12. Click the 'Send message' button.<br/>
'''Expected result:''' The Mahara homepage is displayed with a message 'Your message has been sent'.
13. Log in as 'User one'.<br/>
14. Click the hyperlink 'Contact us', which is at the bottom of the page.<br/>
'''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.<br/>
16. Click the 'Send message' button.<br/>
'''Expected result:''' The Mahara dashboard page is displayed with a message 'Your message has been sent'.
-----
<span style="background:#e3baba">'''BUG 1772298 - Bug description:''' login help icon hidden on Modern theme</span>
'''Environment to be tested:''' Master<br/>
'''Browser to be tested:''' Chrome <br/>
'''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<br/>
2. User is on the login screen<br/>
'''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.
-----
<span style="background:#e3baba">'''Bug 1734557: Allow SAML plugin to have custom auth error message - like Xmlrpc</span>
'''Environment to be tested:''' Master<br/>
'''Browser to be tested:''' Chrome <br/>
'''Precondition:'''
1. A user with 'Site admin' access exists.<br/>
2. ‘Institution A' exists.<br/>
'''Steps to reproduce:'''
1. Log in as ‘Site admin’.<br/>
2. Navigate to Administration menu > Institutions > Settings.<br/>
3. Click the ‘Settings’ button for ‘Institution A’.<br/>
4. Select ‘SAML’ from the ‘Authentication plugin’ drop-down menu.<br/>
5. Add ‘SAML’ meta data and make sure the 'Authentication login message' is set up with the text ‘This is an error message’.<br/>
6. Click the ‘Submit’ button.<br/>
7. Click the 'Save' button.<br/>
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.<br/>
9. Log out as ‘Site admin’.<br/>
10. Now try to log in as ‘User one’ using the regular login fields and not the SSO button.<br/>
'''Expected result:''' ‘User one’ is not able to log in and the authentication login error message box is displayed: ‘This is an error message’.


-----
-----

Revision as of 12:34, 5 Haziran 2020

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 LogInOutandDashboardDefaultPages


Manual Test Scenario: User should see correct page styling
Primary school theme
Raw theme
File:Default theme - Dashboard - Mahara - 04 - 04 - 2018.png
Default theme
Ocean theme
Modern 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
Registration page Ocean theme
Registration page Modern theme
Registration page Primary school theme
Registration page 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 | [email protected] |
| 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 script scenarios for Profile pages

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



Manual Test script scenarios for Portfolio pages

Manual Test Scenario: User should see correct page styling
Ocean theme
Modern theme
Primary school theme
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 Leap2A import

Manual Test Scenario: User can upload a 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





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



Manual Test Scenario: 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.



Manual Test Scenario: 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



Manual Test script scenarios for Drag N Drop Functionality

Manual Test Scenario: User should be able to drag and drop files to a page for upload
Files Drag N Drop Feature 22-06-18-13-25-43.png
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)







Retrieved from ‘https://wiki.mahara.org/index.php?title=Testing_Area/Manual_regression_testing&oldid=11196’