Actions

Difference between revisions of "Testing Area/Manual regression testing"

From Mahara Wiki

< Testing Area
 
(109 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=Mahara 18.04 user manual section 3. Dashboard=
+
==Manual regression testing==
 +
This page outlines the manual regression testing for Mahara releases (6 monthly; YY.04 and YY.10).
  
To test this page 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. For more information of the dashboard please see Mahara 18.04 user manual section 3. Dashboard. This page will have screenshots of pages using the "Raw" theme. Other themes will need to be tested but will have to be set by the Site admin in the Site settings panel found here '''Admin menu > Configure site > Site options > Site settings'''
+
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 [https://wiki.mahara.org/wiki/Testing_Area/Manual_item_testing 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.
  
== Mahara 18.04 user manual section 3.1 Login==
+
==Manual Regression Testing Preconditions==
'''Assumptions:''' To test this page 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
 
  
<div class="toccolours mw-collapsible mw-expanded" style="background:linen">
+
For manual regression testing it is assumed that:
====Things to test for Manually====
+
# a '''fresh install of Mahara has taken place''' and "Password" and "email" are set for the initial Site admin login
<div class="mw-collapsible-content">
+
# there is '''a fresh database with no data'''
 +
# 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')
 +
# the ''' theme will be (re-)set''' by the Site admin in Admin menu > Configure site > Site options > Site settings
 +
# at least one account (named PersonA) other than the Site admin account is active (via manual individual account add or csv file account creation)
 +
# the default browser (used to take the actual result screen shots) is currently Chrome running on a Windows10 (virtual) machine
 +
# other test platforms include Win10-Edge and Win10-Firefox (OSx-Safari & Android-Chrome if time permits)
 +
# the latest stable browser versions are used.
  
#'''Visual check'''
+
==Manual Regression Testing Scenarios==
## Login page uses correct colour "Raw" <span style="color:red">TODO: We need to find a way to toggle this easily </span>
 
## header elements displayed
 
### Mahara logo displayed -top left of page
 
### Search bar displayed
 
### navigation menus displayed - User menu, Administration menu and Main menu
 
## Static Welcome Page title h1 displayed
 
## Text "Edit this text via "Administration menu" → "Configure site" → "Static pages"." is displayed with link to "Static pages" page
 
## Clicking "Static pages" link - takes user to a Log in to Mahara page with only the Login Block displayed
 
## Static "Quick links" displayed but link functionality suppressed until user logs in
 
## buttons displayed "Login"
 
## fields displayed "Username" & "Password"
 
## Links displayed "Register" & "Lost username / password"
 
## footer is displayed and links functioning correctly
 
#'''User invalid login'''- user should see an error message and will not be logged in<br />
 
#'''User valid login'''- user should be logged in and and redirected to the '''''Dashboard''''' page
 
#'''"Registration"''' link is displayed and functioning
 
#'''"Lost username / password"''' link is displayed and functioning
 
</div>
 
</div>
 
  
<div class="toccolours mw-collapsible mw-collapsed" style="background:ivory">
+
<!--########################################## (LOG IN/LOGGED OUT) 'HOME" pages ###########################################################-->
  
====Automated Test script scenarios====
+
<div class="toccolours mw-collapsible mw-collapsed" style="background:#ffffff">
<div class="mw-collapsible-content">
 
  
<div class="toccolours mw-collapsible mw-collapsed">
+
===Manual test scenarios for LogIn and Logged Out (Homepage) pages===
:::'''Scenario:''' User should see correct page styling
 
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' user is logged in <br />
 
::::'''When''' is on the "Mahara homepage"<br />
 
::::'''Then''' user should see "Raw" theme colours <br />
 
</div>
 
</div>
 
  
 
<div class="toccolours mw-collapsible mw-collapsed">
 
<div class="toccolours mw-collapsible mw-collapsed">
:::'''Scenario:''' User invalid login
+
:::'''Homepage Scenario 1:''' Mahara "Homepage" (log in page) content and styling is correct.
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' user is not logged in <br />
+
{| style="float:right; margin-left: 10px;"
::::'''And''' is on the Mahara homepage<br />
+
|----
::::'''When''' user enters valid username <br />
+
|[[File:Win10-Edge Raw theme - Log InOut - MaharaRel20-10.png|thumb|200px| Raw theme]]
::::'''And''' user enters invalid password <br />
+
|[[File:Win10-Edge Primary school theme - Log InOut - MaharaRel20-10.png|thumb|200px|Primary school theme]]
::::'''Then''' user should see "You have not provided the correct credentials to log in. Please check your username and password are correct." error message<br />
+
|[[File:Win10-Edge Default theme - Log InOut - MaharaRel20-10.png|thumb|200px|Default theme]]
::::'''And''' user should see "There was an error with submitting this form. Please check the marked fields and try again."<br />
+
|[[File:Win10-Edge Ocean theme - Log InOut - MaharaRel20-10.png|thumb|200px|Ocean theme]]
::::'''And''' user will not be logged in
+
|[[File:Win10-Edge Modern theme - Log InOut - MaharaRel20-10.png|thumb|200px|Modern theme]]
 +
|[[File:Win10-Edge Maroon theme - Log InOut - MaharaRel20-10.png|thumb|200px|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.
 +
<!-- <span style="color:red">Compare the page with the screenshots for correct theme colours, fonts and style. </span> -->
 
</div>
 
</div>
 
</div>
 
</div>
  
 
<div class="toccolours mw-collapsible mw-collapsed">
 
<div class="toccolours mw-collapsible mw-collapsed">
:::'''Scenario:''' "Registration" links to "Registration" page
+
:::'''Homepage Scenario 2:''' PersonA can successfully reset their Mahara password.
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' user is not logged in <br />
+
{| style="float:right; margin-left: 10px;"
::::'''And''' is on the "Mahara homepage"<br />
+
|----
::::'''When''' user clicks "Registration" link <br />
+
|[[File:ResetLoginEmail_06_04_18_05-59-52.png|thumb|200px|Reset Email Instructions]]
::::'''Then''' user should be on the "Registration" page<br />
+
|----
 +
|}
 +
::::'''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 <span style="color:red"> - manually inspect inbox to ensure email was sent and is correct.</span>
 +
::::'''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
 
</div>
 
</div>
 
</div>
 
</div>
  
 
<div class="toccolours mw-collapsible mw-collapsed">
 
<div class="toccolours mw-collapsible mw-collapsed">
:::'''Scenario:''' "Lost username / password" links to "Forgotten your username or password?" page
+
:::'''Homepage Scenario 3:''' Logged out person should see correct page content and styling
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' user is not logged in <br />
+
{| style="float:right; margin-left: 10px;"
::::'''And''' is on the "Mahara homepage" <br />
+
|----
::::'''When''' user clicks the "Lost username / password" link <br />
+
|[[File:Raw theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px| Raw theme]]
::::'''Then''' user should be on the "Forgotten your username or password?" page  
+
|[[File:Primary school theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Primary school theme]]
 +
|[[File:Default theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Default theme]]
 +
|[[File:Ocean theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Ocean theme]]
 +
|[[File:Modern theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|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.
 +
<!-- <span style="color:red">Compare the page with the screenshots for correct theme colours</span> -->
 
</div>
 
</div>
 
</div>
 
</div>
  
<div class="toccolours mw-collapsible mw-collapsed">
 
:::'''Scenario:''' User valid login
 
<div class="mw-collapsible-content">
 
::::'''Given''' user is not logged in <br />
 
::::'''And''' is on the "Mahara homepage"<br />
 
::::'''When''' user enters valid username <br />
 
::::'''And''' user enters valid password <br />
 
::::'''Then''' user should be on the "Dashboard" page <br />
 
::::'''And''' user will be logged in</div>
 
</div>
 
</div>
 
 
</div>
 
</div>
  
<!-- ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////-->
+
<!--#################################################### DASHBOARD page ###############################################################-->
== Mahara 18.04 user manual section 3.2 Login with strict privacy==
+
<div class="toccolours mw-collapsible mw-collapsed" style="background:#ffffff">
  
'''Assumptions:''' To test this page 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
+
===Manual test scenarios for [default] Dashboard page===
 +
<div class="mw-collapsible-content">
  
<div class="toccolours mw-collapsible mw-expanded" style="background:linen">
+
<div class="toccolours mw-collapsible mw-collapsed">
====Things to test for Manually====
+
:::'''Dashboard Scenario 1:''' Site admin should see correct Dashboard page content and styling
<span style="color:red">TODO: </span>
 
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
This is where test criteria go
+
{| style="float:right; margin-left: 10px;"
 +
|----
 +
|[[File:Raw theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px| Raw theme]]
 +
|[[File:Primary school theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Primary school theme]]
 +
|[[File:Default theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Default theme]]
 +
|[[File:Ocean theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Ocean theme]]
 +
|[[File:Modern theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|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.
 +
<!-- <span style="color:red">Compare the page with the screenshots for correct theme colours</span> -->
 +
 
 
</div>
 
</div>
 
</div>
 
</div>
  
<div class="toccolours mw-collapsible mw-collapsed" style="background:ivory">
+
<div class="toccolours mw-collapsible mw-collapsed">
====Automated Test script scenarios====
+
:::'''Dashboard Scenario 2:''' PersonA (non-admin) should see correct Dashboard page content and styling
<span style="color:red">TODO: </span>
 
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
This is where Automated test scenarios go
+
{| style="float:right; margin-left: 10px;"
 +
|----
 +
|[[File:Raw theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px| Raw theme]]
 +
|[[File:Primary school theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Primary school theme]]
 +
|[[File:Default theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Default theme]]
 +
|[[File:Ocean theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|Ocean theme]]
 +
|[[File:Modern theme - Dashboard - Mahara - 04 - 04 - 2018.png|thumb|200px|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.
 +
<!-- <span style="color:red">Compare the page with the screenshots for correct theme colours</span> -->
 +
 
 
</div>
 
</div>
 
</div>
 
</div>
<!-- ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////-->
 
  
 +
</div>
  
==Mahara 18.04 user manual section 3.3 Overview page==
+
<!--##################################################### PROFILE page ###################################################################-->
 +
<div class="toccolours mw-collapsible mw-collapsed" style="background:#ffffff">
  
'''Assumptions:''' To test this page 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
+
===Manual test scenarios for [default] Profile page===
 +
<div class="mw-collapsible-content">
  
<div class="toccolours mw-collapsible mw-expanded" style="background:linen">
+
<div class="toccolours mw-collapsible mw-collapsed">
====Things to test for Manually====
+
:::'''Profile scenario 1:''' PersonA should see correct page content and styling on their default Profile page.
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
 +
 +
{| style="float:right; margin-left: 10px;"
 +
|----
 +
|[[File:Profile-About_Me-Mahara-Raw.png|thumb|200px|Raw theme]]
 +
|[[File:Profile-About_Me-Mahara-Primary_school.png|thumb|200px|Primary school theme]]
 +
|[[File:Profile-About_Me-Mahara-Default.png|thumb|200px|Default theme]]
 +
|[[File:Profile-About_Me-Mahara-Modern.png|thumb|200px|Modern theme]]
 +
|[[File:Profile-About_Me-Mahara-Ocean.png|thumb|200px|Ocean theme]]
 +
|----
 +
|}
  
 
#'''Visual check'''
 
#'''Visual check'''
## Login page uses correct colour "Raw"  
+
## Profile page uses correct colour "Raw"  
 
## header elements displayed  
 
## header elements displayed  
## Welcome Page title h1 displayed
+
## Static Profile Page title h1 displayed
## Text "Edit this text via "Administration menu" → "Configure site" → "Static pages"." is displayed with link to "Static pages" page
 
## "Quick links" block is displayed with correct links to respective pages
 
## user info block displayed
 
 
## online users block displayed
 
## online users block displayed
## Latest changes I can view block displayed
 
## My portfolios block displayed
 
## Inbox block displayed
 
## Topics I am following block displayed
 
## Watched pages block displayed
 
 
## footer is displayed and links functioning correctly
 
## footer is displayed and links functioning correctly
 
# '''Change page "Layout" functionality works'''
 
# '''Change page "Layout" functionality works'''
Line 140: Line 172:
 
# '''Page edit functionality works''' Create edit and delete page blocks
 
# '''Page edit functionality works''' Create edit and delete page blocks
 
# '''Page links working''' Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"
 
# '''Page links working''' Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"
 +
 
</div>
 
</div>
 
</div>
 
</div>
  
<div class="toccolours mw-collapsible mw-collapsed" style="background:ivory">
+
<div class="toccolours mw-collapsible mw-collapsed">
 +
:::'''Profile scenario 2:''' Multiple Email Functionality
 +
<div class="mw-collapsible-content">
 +
{| style="float:right; margin-left: 10px;"
 +
|----
 +
|[[File:Primary_email_error_message_24-05-18-10-09-53.png|thumb|200px|Multiple Email]]
 +
|----
 +
|}
 +
::::'''Scenario:''' <span style="color:blue">Only one email address:</span> 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
  
====Automated Test script scenarios====
+
::::'''Scenario:''' <span style="color:blue">One or more email addresses:</span> 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.
<div class="mw-collapsible-content">
+
 
 +
{| style="float:right; margin-left: 10px;"
 +
|----
 +
|[[File:MultipleEmailAddresses_24-05-18-10-04-01.png|thumb|200px|Multiple Email Addresses]]
 +
|----
 +
|}
  
<div class="toccolours mw-collapsible mw-collapsed">
+
::::'''Given''' user logged in
:::'''Scenario:''' User should see correct page styling
+
::::'''And''' has more than one email address
<div class="mw-collapsible-content">
+
::::'''And''' user has validated the email mail address 
::::'''Given''' user is logged in <br />
+
::::'''When''' user is on the Profile > Contact information page
::::'''Then''' user should be on "Dashboard" page<br />
+
::::'''And''' user has selected the second email address
::::'''And''' user should see "Raw" theme colours <br />
+
::::'''And''' clicks the delete icon associated with the first email in the list
::::'''Then''' automation script take screenshot
+
::::'''And''' then the first email in the list will be deleted
::::'''And''' save the file in "Local folder"
 
 
</div>
 
</div>
 
</div>
 
</div>
  
<div class="toccolours mw-collapsible mw-collapsed">
+
</div>
:::'''Scenario:''' User click "More" link to see more messages
+
</div>
<div class="mw-collapsible-content">
 
:::'''Bagkground:'''
 
  
<span style="color:red">TODO: Create step definition to populate DB with 60 messages</span>
+
<!--##################################################### CREATE pages ##################################################################-->
 +
<div class="toccolours mw-collapsible mw-collapsed" style="background:#ffffff">
  
::::'''Given''' the following "60""Messages" exist:
+
===Manual test scenarios for Create pages===
::::::| |  |
+
<div class="mw-collapsible-content">
::::'''Given''' user is logged in <br />
 
::::'''When''' user is on the "Dashboard"<br />
 
::::'''Then''' user should see "Inbox" block <br />
 
::::'''When''' I follow "More" <br />
 
::::'''And''' I select 10 from Results per page:
 
::::'''Then''' I should be on "Notifications" page <br />
 
::::'''And''' I should see 10 messages displayed </br>
 
::::'''And''' I should see pagination
 
</div>
 
</div>
 
  
 
<div class="toccolours mw-collapsible mw-collapsed">
 
<div class="toccolours mw-collapsible mw-collapsed">
:::'''Scenario:''' User changes Page layout from 2 column to 3 column layout
+
:::'''Create Pages and Collections scenario 1 :''' PersonA should see correct page content and styling on their default Create 'Pages and Collections' home page
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' Some preconditions <br />
+
{| style="float:right; margin-left: 10px;"
::::'''When''' user performs some action <br />
+
|----
::::'''Then''' Something should happen
+
|[[File:PortfolioOverviewRaw_18-05-18-14-29-30.png|thumb|200px|Raw theme]]
 +
|[[File:PortfolioOverviewPrimarySchool_18-05-18-14-29-30.png|thumb|200px|Primary school theme]]
 +
|[[File:PortfolioOverviewDefault_18-05-18-14-29-30.png|thumb|200px|Default theme]]
 +
|[[File:PortfolioOverviewModern_18-05-18-14-29-30.png|thumb|200px|Ocean theme]]
 +
|[[File:PortfolioOverviewOcean_18-05-18-14-29-30.png|thumb|200px|Modern theme]]
 +
|----
 +
|}
 +
#'''Visual check'''
 +
## Profile page uses correct colour "Raw"
 +
## header elements displayed
 +
## Static Profile Page title h1 displayed
 +
## online users block displayed
 +
## footer is displayed and links functioning correctly
 +
# '''Change page "Layout" functionality works'''
 +
# '''Change page "Skin" functionality works'''
 +
# '''Page edit functionality works''' Create edit and delete page blocks
 +
# '''Page links working''' Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"
 
</div>
 
</div>
 
</div>
 
</div>
  
 
<div class="toccolours mw-collapsible mw-collapsed">
 
<div class="toccolours mw-collapsible mw-collapsed">
:::'''Scenario:''' User changes the page skin from default "Raw" pre-made site skin
+
:::'''Create Files scenario 1:''' PersonA should see correct page content and styling on their default Create 'Files' home page
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' Some preconditions <br />
+
{| style="float:right; margin-left: 10px;"
::::'''When''' user performs some action <br />
+
|----
::::'''Then''' Something should happen <br />
+
|[[File:Files_page_24-05-18-10-52-37.png|thumb|200px]]
 +
|----
 +
|}
 +
#'''Visual check'''
 +
## Profile page uses correct colour "Raw"
 +
## header elements displayed
 +
## Static Profile Page title h1 displayed
 +
## online users block displayed
 +
## footer is displayed and links functioning correctly
 +
# '''Change page "Layout" functionality works'''
 +
# '''Change page "Skin" functionality works'''
 +
# '''Page edit functionality works''' Create edit and delete page blocks
 +
# '''Page links working''' Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"
 
</div>
 
</div>
 
</div>
 
</div>
  
 
<div class="toccolours mw-collapsible mw-collapsed">
 
<div class="toccolours mw-collapsible mw-collapsed">
:::'''Scenario:''' User adds block to page, edits new block and deletes block from page
+
:::'''Create Files scenario 2:''' User "Quota" block updates as files are added
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' Some preconditions <br />
+
# Confirm that when files are added the '''Quota block updates''' and the display bar is filled in accordingly.
::::'''When''' user performs some action <br />
+
 
::::'''Then''' Something should happen <br />
 
 
</div>
 
</div>
 
</div>
 
</div>
  
 
<div class="toccolours mw-collapsible mw-collapsed">
 
<div class="toccolours mw-collapsible mw-collapsed">
:::'''Scenario:''' User wants to do something
+
:::'''Create Files scenario 3:''' Image files can be edited and rotated
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
::::'''Given''' Some preconditions <br />
 
::::'''When''' user performs some action <br />
 
::::'''Then''' Something should happen <br /></div>
 
</div>
 
</div>
 
</div>
 
<!-- ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////-->
 
  
== Mahara 18.04 user manual section 3.4. Navigation==
+
::'''Preconditions:'''
 +
::# User has Image files loaded into Mahara
 +
::# User has document files loaded into Mahara  
  
'''Assumptions:''' To test this page 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
+
::'''Test Script:'''
 +
::# User browse to Main menu > Content > Files
 +
::# User edit an Image file by clicking the pencil icon to right of image file
 +
::# Confirm there is an rotate icon to right of image in the Edit file section of the page
 +
::# Click the rotate icon
 +
::# Confirm that the image preview rotates 1/4 turn to the right each time the rotate icon is clicked
 +
::#
  
<div class="toccolours mw-collapsible mw-expanded" style="background:linen">
 
====Things to test for Manually====
 
<span style="color:red">TODO: </span>
 
<div class="mw-collapsible-content">
 
This is where test criteria go
 
 
</div>
 
</div>
 
</div>
 
</div>
  
<div class="toccolours mw-collapsible mw-collapsed" style="background:ivory">
+
<!--##################################################### Drag N Drop ############################################################-->
====Automated Test script scenarios====
+
<div class="toccolours mw-collapsible mw-collapsed">
<span style="color:red">TODO: </span>
+
:::'''Create Files scenario 3:''' User should be able to drag and drop files to a page for upload
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
This is where Automated test scenarios go
+
{| style="float:right; margin-left: 10px;"
</div>
+
|----
</div>
+
|[[File:Files_Drag_N_Drop_Feature_22-06-18-13-25-43.png|thumb|200px]]
<!-- ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////-->
+
|----
 
+
|}
 
 
  
== Mahara 18.04 user manual section 3.5. Quick links==
+
::'''Preconditions:'''
 +
::# User has Image files on their local machine
 +
::# User has document files on their local machine
  
'''Assumptions:''' To test this page 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
+
::'''Test Script:'''
 +
::# User browse to Main menu > Content > Files
 +
::# Confirm that there is a "Drop files here to upload" section on the page
 +
::# User open the file browser for their local machine
 +
::# User browse to a file to upload to Mahara 
 +
::# using the cursor, hover over the desired file
 +
::# click and hold while draging the file to the dark grey Drag N Drop section of the Page
 +
::# release the click
 +
::# Confirm that the file is uploaded and a message is displayed as follows :Upload of <file name> complete
 +
::# Repeat the above steps for different file types that Mahara will accept (ie.. image file types jpg png, document file types docx, PDF)
  
<div class="toccolours mw-collapsible mw-expanded" style="background:linen">
 
====Things to test for Manually====
 
<span style="color:red">TODO: </span>
 
<div class="mw-collapsible-content">
 
This is where test criteria go
 
 
</div>
 
</div>
 
</div>
 
</div>
  
<div class="toccolours mw-collapsible mw-collapsed" style="background:ivory">
+
<div class="toccolours mw-collapsible mw-collapsed">
====Automated Test script scenarios====
+
:::'''Create Skins scenario 1 :''' PersonA should see correct page content and styling on their default Create 'Skins' home page
<span style="color:red">TODO: </span>
 
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
This is where Automated test scenarios go
 
</div>
 
</div>
 
<!-- ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////-->
 
  
== Mahara 18.04 user manual section 3.6. User-specific information==
+
{| style="float:right; margin-left: 10px;"
 +
|----
 +
|[[File:PortfolioOverviewRaw_18-05-18-14-29-30.png|thumb|200px|Raw theme]]
 +
|[[File:PortfolioOverviewPrimarySchool_18-05-18-14-29-30.png|thumb|200px|Primary school theme]]
 +
|[[File:PortfolioOverviewDefault_18-05-18-14-29-30.png|thumb|200px|Default theme]]
 +
|[[File:PortfolioOverviewModern_18-05-18-14-29-30.png|thumb|200px|Ocean theme]]
 +
|[[File:PortfolioOverviewOcean_18-05-18-14-29-30.png|thumb|200px|Modern theme]]
 +
|----
 +
|}
  
'''Assumptions:''' To test this page 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
+
#'''Visual check'''
 +
## Profile page uses correct colour "Raw"
 +
## header elements displayed
 +
## Static Profile Page title h1 displayed
 +
## online users block displayed
 +
## footer is displayed and links functioning correctly
 +
# '''Change page "Layout" functionality works'''
 +
# '''Change page "Skin" functionality works'''
 +
# '''Page edit functionality works''' Create edit and delete page blocks
 +
# '''Page links working''' Tester can use Chrome extension Link Checker or dev tools to determine "200 code return"
  
<div class="toccolours mw-collapsible mw-expanded" style="background:linen">
 
====Things to test for Manually====
 
<span style="color:red">TODO: </span>
 
<div class="mw-collapsible-content">
 
This is where test criteria go
 
 
</div>
 
</div>
 
</div>
 
</div>
 
<div class="toccolours mw-collapsible mw-collapsed" style="background:ivory">
 
====Automated Test script scenarios====
 
<span style="color:red">TODO: </span>
 
<div class="mw-collapsible-content">
 
This is where Automated test scenarios go
 
 
</div>
 
</div>
 
</div>
 
</div>
<!-- ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////-->
 
  
== Mahara 18.04 user manual section 3.7. Footer==
+
<!--##################################################### MANAGE ###########################################################-->
 +
<div class="toccolours mw-collapsible mw-collapsed" style="background:#ffffff">
  
'''Assumptions:''' To test this page 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
+
===Manual test scenarios for 'Manage'===
 +
<div class="mw-collapsible-content">
  
<div class="toccolours mw-collapsible mw-expanded" style="background:linen">
+
<div class="toccolours mw-collapsible mw-collapsed">
====Things to test for Manually====
+
:::'''Upload Leap2A file scenario 1:''' User can upload an Leap2A file
<span style="color:red">TODO: </span>
 
 
<div class="mw-collapsible-content">
 
<div class="mw-collapsible-content">
This is where test criteria go
+
 
 +
{| style="float:right; margin-left: 10px;"
 +
|----
 +
|[[File:Import_leap2a_08-06-18-11-19-06.png|thumb|200px|Leap2a import page]]
 +
|[[File:Import_leap2a_choose_items_08-06-18-11-08-46.png|thumb|200px|Leap2A imported data]]
 +
|----
 +
|}
 +
'''Preconditions:'''
 +
# User has a Leap2A zip file from a previous export of all of "Admin User" data.
 +
# user has unzipped the file which should include 
 +
## files folder containing image files, document files that have been used on users's profile/portfolio
 +
## leap2a.xml file
 +
'''Test Script:'''
 +
# user (someone other than admin) log in
 +
# Browse to Main menu > Portfolio > Import
 +
# Click the choose a file and upload the "leap2a.xml" file of the Admin User profile
 +
# Click the import button
 +
# Confirm you see the all the data that will be imported
 +
# Select the information you want to ignore, append, replace or add new
 +
# click the "Import" button
 +
# Note that you will have to upload the files into the folders
 +
# view the areas that you have added ie Portfolio pages
 +
# confirm that the new pages are displayed with the content on the pages
 +
 
 
</div>
 
</div>
 
</div>
 
</div>
 
<div class="toccolours mw-collapsible mw-collapsed" style="background:ivory">
 
====Automated Test script scenarios====
 
<span style="color:red">TODO: </span>
 
<div class="mw-collapsible-content">
 
This is where Automated test scenarios go
 
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 14:10, 12 November 2020

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

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

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.
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
Homepage Scenario 3: Logged out person should see correct page content and styling
Raw theme
Primary school 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.

Manual test scenarios for [default] Dashboard page

Dashboard Scenario 1: Site admin should see correct Dashboard page content and styling
Raw theme
Primary school 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.
Dashboard Scenario 2: PersonA (non-admin) should see correct Dashboard page content and styling
Raw theme
Primary school 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.

Manual test scenarios for [default] Profile page

Profile scenario 1: PersonA should see correct page content and styling on their default Profile page.
Primary school 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"
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

Manual test scenarios for Create pages

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
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"
Create Files scenario 1: PersonA should see correct page content and styling on their default Create 'Files' home page
Files page 24-05-18-10-52-37.png
  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"
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.
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
Create Files scenario 3: 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)
Create Skins scenario 1 : PersonA should see correct page content and styling on their default Create 'Skins' home page
Raw theme
Primary school 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"

Manual test scenarios for 'Manage'

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