Test Case Report
Introduction
MUENGAGE is a social media platform for MU that allows the university community to find organizations and events on the university campus. It has tools that help members of the community interact with each other and track the engagement and or involvement of members within various organizations and campus groups.
The platform has a search engine that allows members to search for various events and information about these events to interact with other community members. This makes it easier when looking for specific content that concerns the person. a page exists that contains information about the organization and allows a student to register or enroll as a member in the organization.
The platform allows users to see all upcoming events in every organization and as well shows service or volunteer activities that the student can get involved in. In the same light, the platform allows for tracking of membership with a tool called My Memberships.
Lastly, MUENGAGE allows community members to update their profile information and track involvement in their memberships which allows them to know how active they are in various organizations in the University.
The features that will be considered for testing are as follows:
- Logging in to the portal
- Searching the portal for organizations
- The validity of links on the platform
- The relevance of information provided on the platform
- The availability of content on the page especially when one changes pages
Test-Case Report Structure
The structure of the test-case report of the environment to be tested is as follows:
- Types of software tests to be considered for the platform and their purpose in the platform
- Two to four test-cases and their purpose
- Introduction and descriptiorpose
- Exit Criteria – the conditions that must be fulfilled to successfully conclude the testing cycle or exercise
- Test case template for the tests to be done on each test element on the platform.
Types of Tests to be considered
Boundary Value Analysis (BVA): To define the testing of boundaries for a specified range of values.
State Transition Technique: To test for software behavior changes from one state to another following particular action. For example when one edits records in the Profile section to check if the data has updated on the platform.
Error Guessing Technique: This is guessing/anticipating the error that may arise while doing manual testing.
Test #1
| Test Case Number | 1 | Test Case Name | Test user login with MUID and password | ||||||||
| Test Case Type | Validation Test/State Transition Test | ||||||||||
| S # | Entry Criteria | S # | Test Data Requirement | ||||||||
| 1 | Availability of Internet | 1 | A user inputs a correct MUID | ||||||||
| 2 | Possession of a valid MUID | 2 | A user inputs a password | ||||||||
| 3 | Possession of a valid Password | 3 | A user can login | ||||||||
| 4 | 4 | ||||||||||
| Test Conditions | |||||||||||
| Step # | Step Details | Expected Results | Actual Results | Pass / Fail / Not executed / Suspended | |||||||
| 1 | Enter an invalid MUID | Error on form field | No error on form field | Fail | |||||||
| 2 | Enter a valid MUID | No error on form field | No error on form field | Pass | |||||||
| 3 | Enter an invalid password | No error on form field | No error on form field | Pass | |||||||
| 4 | Enter a valid Password | No error on form field | No error on form field | Pass | |||||||
| 5 | Enter a correct MUID and password | Logs in to the platform | Logs in to the platform | Pass | |||||||
Test #2
| Test Case Number | 2 | Test Case Name | Test search bar | ||||||||
| Test Case Type | Validation Test/ Error guessing | ||||||||||
| S # | Entry Criteria | S # | Test Data Requirement | ||||||||
| 1 | Availability of Internet | 1 | A user inputs correct search criteria | ||||||||
| 2 | Correct Search Query | 2 | A user inputs some text | ||||||||
| 3 | 3 | ||||||||||
| 4 | 4 | ||||||||||
| Test Conditions | |||||||||||
| Step # | Step Details | Expected Results | Actual Results | Pass / Fail / Not executed / Suspended | |||||||
| 1 | Press search for an empty search | No results found message | No Results found message | Pass | |||||||
| 2 | Pass a wrong search query | No results found message | No Results found message | Pass | |||||||
| 3 | Pass a correct search query : baseball | Baseball events | Baseball events | Pass | |||||||
Test #3
| Test Case Number | 3 | Test Case Name | Check if links are functioning correctly | ||||||||
| Test Case Type | State Transition Test | ||||||||||
| S # | Entry Criteria | S # | Test Data Requirement | ||||||||
| 1 | Availability of Internet | 1 | A user clicks a link | ||||||||
| 2 | A user is redirected to the appropriate page | ||||||||||
| Test Conditions | |||||||||||
| Step # | Step Details | Expected Results | Actual Results | Pass / Fail / Not executed / Suspended | |||||||
| 1 | Click a link | Redirect to appropriate page | Redirects to appropriate page | Pass | |||||||
| 2 | Clicks a link | Click works | Click works | Pass | |||||||
Test #4
| Test Case Number | 4 | Test Case Name | Enroll to an event | ||||||||
| Test Case Type | Validation Test/State Transition Test | ||||||||||
| S # | Entry Criteria | S # | Test Data Requirement | ||||||||
| 1 | Availability of Internet | 1 | A user searches and finds an event | ||||||||
| 2 | Be logged in | 2 | A enrolls | ||||||||
| 3 | 3 | A user can see they are enrolled | |||||||||
| 4 | 4 | ||||||||||
| Test Conditions | |||||||||||
| Step # | Step Details | Expected Results | Actual Results | Pass / Fail / Not executed / Suspended | |||||||
| 1 | Search for valid event | Find event | Found event: baseball | Pass | |||||||
| 2 | Enroll for event | Page redirects and shows enrolled | Page redirects and shows enrolled | Pass | |||||||
| 3 | Search for an invalid event | No results found | No results found | Pass | |||||||