Testing Area/Manual regression testing
From Mahara Wiki
< Testing Area
Manual Test Cases
Dashboard Manual Testing
To test this page it is assumed that a fresh install of Mahara has taken place and that there is a fresh database. 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
Login page
Things to test for
- Visual check
- Login page uses correct colour
- Mahara logo displayed -top left of page
- 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
- 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
Automated 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: 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
- 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
Overview page
To test this page it is assumed that a fresh install of Mahara has taken place and that there is a fresh database.
Things to test for
- Visual check
- Page styling correct colour
- Raw theme
- Primary School theme
- Ocean theme
- Default blocks displayed
- Page styling correct colour
- Page edit functionality works Create edit and delete page blocks
- Other page functionality Block pagination
- Page links working
Manual 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 can see messages in "Inbox" block
- Given user is logged in
- When user is on the "Dashboard"
- Then user should see "Inbox" block
- Given user is logged in
- Scenario: User click "More" link to see more messages
- Bagkground:
TODO: Create step definition
- Given the following "20""Messages" exist:
- | | |
- Given the following "20""Messages" exist:
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions
- Scenario: User
- Given Some preconditions
- When user performs some action
- Then Something should happen
- Given Some preconditions