Test-case report

OrgSync is MU’s social media platform enables the university community to find organizations and events on the university campus. The platform has numerous tools for interacting with members within organizations as well as tracking the level of engagement or involvement of members within various campus groups. This platform is found on MU’s portal or https://orgsync.com/login/marymount-university. Below is a screen shot of OrgSync’s home page.

The platform was several features:

· A search engine on the landing page for registered members to look up specific information about events on campus.

· Top navigation bar with links to registered student organizations, events and service opportunities.

· Left sidebar that displays featured events on campus which are sponsored by various student organizations and university departments

· There is also a right sidebar shows upcoming events on campus and service or volunteer opportunities.

· A tool for members to enroll in organizations of their choice and also track their membership. This tool is called My Memberships.

· Under the Profile name is a set tools for updating profile information, tracking involvement, and communicating with other registered members.

Required:

The project has 2 components: a test-case report and presentation:

a) Report

Prepare a test-case report on any features of your choice which are in OrgSync. The test case report, which should be at least 8 pages, should have the following:

· An introduction describing the purpose of OrgSync in MU community as well as the features that your report will consider for testing. In the introduction, the last paragraph should describe the structure of your test-case report.

· A description of the test environment for conducting the tests

· The types of software tests you will consider and their purpose

· 10 Test cases (use the template below for each test case)

· Exit Criteria – conditions that must be fulfilled to successfully conclude the testing cycle or exercise.

Description of the components in the above the test case template:

· Test case # - since you are required to have 10 test cases for each template, just use running numbers e.g. 1 if you are working on the first test case and so forth

· Test case name – state the name of the test case e.g. login with MU ID and password, etc

· Type of test case – this should be either functional or nonfunctional requirement. You will need to figure this out for each test case since you can now differentiate between functional and non-functional requirements. First start with the functional requirements and then conclude with non-functional requirements.

· Test scenario – a list of logical steps that you will perform when conducting each test.

· Test data – data that will be used to test the application. For password related data, please do not use your actual passwords or usernames – make up something for purposes of this project. Also don’t use actual personally identically information like phone numbers, addresses, etc.

· Expected result – expected behavior or outcome when that test is performed.

· Entry Criteria – conditions that must exist for the test to be conducted e.g. the availability of internet to conduct the test for the login interface, etc. You can add additional conditions.

b) Presentation

Prepare a PowerPoint presentation from your report that should not take more than 5 minutes. The presentation should have a short description of OrgSync, one type of test you considered among several which are in the report, and two test cases out of the ten which are in the report.

Rubric

Page 3 of 3