Testing/Manual testing/Dashboard
From Mahara Wiki
< Testing
Mahara 18.04 user manual section 3. Dashboard
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
Mahara 18.04 user manual section 3.1 Login
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
Things to test for Manually
- Visual check
- Login page uses correct colour "Raw" TODO: We need to find a way to toggle this easily
- 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
- 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
Test script scenarios
- Scenario: User should see correct page styling
- Given user is logged in
- When is on the "Mahara homepage"
- Then user should see "Raw" theme colours
- Given user is logged in
- Scenario: User invalid login
- Given user is not logged in
- And is on the Mahara homepage
- When user enters valid username
- And user enters invalid password
- Then user should see "You have not provided the correct credentials to log in. Please check your username and password are correct." error message
- And user should see "There was an error with submitting this form. Please check the marked fields and try again."
- And user will not be logged in
- Given user is not logged in
- Scenario: "Registration" links to "Registration" page
- Given user is not logged in
- And is on the "Mahara homepage"
- When user clicks "Registration" link
- Then user should be on the "Registration" page
- Given user is not logged in
- Scenario: "Lost username / password" links to "Forgotten your username or password?" page
- Given user is not logged in
- And is on the "Mahara homepage"
- When user clicks the "Lost username / password" link
- Then user should be on the "Forgotten your username or password?" page
- Given user is not logged in
- Scenario: User valid login
- Given user is not logged in
- And is on the "Mahara homepage"
- When user enters valid username
- And user enters valid password
- Then user should be on the "Dashboard" page
- And user will be logged in
- Given user is not logged in
Mahara 18.04 user manual section 3.2 Login with strict privacy
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
Things to test for Manually
TODO:
Test script scenarios
TODO:
This is where Automated test scenarios go
Mahara 18.04 user manual section 3.3 Overview page
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
Things to test for Manually
- Visual check
- Login page uses correct colour "Raw"
- header elements displayed
- Welcome 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
- 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
- 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"
Test script scenarios
- Scenario: User should see correct page styling
- Given user is logged in
- Then user should be on "Dashboard" page
- And user should see "Raw" theme colours
- Then automation script take screenshot
- And save the file in "Local folder"
- Given user is logged in
- Scenario: User click "More" link to see more messages
- Bagkground:
TODO: Create step definition to populate DB with 60 messages
- Given the following "60""Messages" exist:
- | | |
- Given user is logged in
- When user is on the "Dashboard"
- Then user should see "Inbox" block
- When I follow "More"
- And I select 10 from Results per page:
- Then I should be on "Notifications" page
- And I should see 10 messages displayed
- And I should see pagination
- Given the following "60""Messages" exist:
- Scenario: User changes Page layout from 2 column to 3 column layout
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User changes the page skin from default "Raw" pre-made site skin
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User adds block to page, edits new block and deletes block from page
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User wants to do something
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some 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
Things to test for Manually
- Visual check three new boxes with quick links displayed
- Create (Develop your Portfolio)
- Share (Control your privacy)
- Engage (find people and join groups
- hover state functionality
- Verify links redirect to their respective pages
- Create = Pages and collections page
- Share = Share page
- Engage = Find groups page
- Hide information box - link to remove block
NOTE: This block will look very different depending on the theme used
Test script scenarios
TODO:
This is where Automated test scenarios go
Mahara 18.04 user manual section 3.5. Quick links
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
Things to test for Manually
TODO:
This is where test criteria go
Test script scenarios
TODO:
This is where Automated test scenarios go
Mahara 18.04 user manual section 3.6. User-specific information
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
Things to test for Manually
TODO:
This is where test criteria go
Test script scenarios
TODO:
This is where Automated test scenarios go
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
Things to test for Manually
TODO:
This is where test criteria go
Test script scenarios
TODO:
This is where Automated test scenarios go