IT 355 Project: Engage, MU’s Social Media Platform Enabled ✓ Solved

IT 355 PROJECT Engage is MU’s social media platform enables

IT 355 PROJECT Engage is MU’s social media platform that enables the university community to find organizations and events on the university campus. The platform includes various tools for interacting with members within organizations and tracking the level of engagement or involvement of members within various campus groups. Notably, the platform offers features such as:

  • Discovering and joining new student organizations and discussions on campus
  • Discovering and attending events on campus
  • Tracking involvement in activities and membership in organizations on campus

Required: The project consists of two components: a test-case report and a presentation.

a) Report: Prepare a test-case report on any features of your choice that are included in Engage. The test case report should have the following:

  1. An introduction describing the purpose of Engage in the MU community and the features that your report will consider for testing. The introduction should conclude with a paragraph outlining the structure of your test-case report.
  2. A description of the test environment for conducting the tests.
  3. The types of software tests you will consider and their purpose.
  4. 10 Test cases using the specified template for each test case.
  5. Exit Criteria: conditions that must be fulfilled to successfully conclude the testing cycle or exercise.

Each test case should include:

  • Test case number: Use running numbers (e.g., 1, 2, 3, etc.) for each test case.
  • Test case name: State the name of the test case (e.g., login with MU ID and password).
  • Type of test: This should be either functional or non-functional. Differentiate between functional and non-functional requirements for each test case.
  • Test scenario: A list of logical steps that you will perform for each test.
  • Test data: Data to be used for testing the application. Use fictitious data to protect personal information.
  • Expected result: The expected behavior or outcome upon performing the test.
  • Entry criteria: Conditions that must exist for the test to be conducted (e.g., internet availability).

Paper For Above Instructions

Introduction

The IT 355 PROJECT Engage serves as an integral platform for the university community at MU, enabling students, faculty, and staff to access and participate in various organizations and events on campus. The Engage platform not only enhances connectivity among university members but also allows for tracking involvement in activities. This report will focus on testing three specific features of the Engage platform: creating a new student organization, joining an existing organization, and RSVPing for campus events. The structure of this test-case report includes an overview of the test environment, types of software tests considered, detailed test cases, and defined exit criteria.

Test Environment

The testing will be conducted in a controlled environment to ensure accuracy and reliability. The test environment will consist of:

  • A stable internet connection
  • Access to the Engage platform through MU's portal
  • A compatible web browser (e.g., Chrome, Firefox)
  • A set of test user accounts with varying levels of access

This setup aims to simulate real-world scenarios that users may encounter while interacting with the platform.

Types of Software Tests

The report will consider both functional and non-functional testing. Functional testing focuses on the correctness of the features as per specifications. Non-functional testing will address performance, usability, and security aspects:

  • Functional Tests: These will verify that users can successfully create organizations, join them, and RSVP to events.
  • Non-Functional Tests: These will evaluate the system's performance under load, the usability of the user interface, and security measures in place to protect user data.

Test Cases

Below are the ten test cases that will be utilized for our testing objectives:

  1. Test Case #1

    Test Case Name: Create New Organization

    Test Case ID: TC001

    Type of Test: Functional

    Test Scenario: User navigates to the 'Create Organization' section and fills out the form.

    Test Data: Organization Name: "Tech Club", Description: "A club for tech enthusiasts"

    Expected Result: The system should successfully create the organization and display a confirmation message.

    Entry Criteria: User must be logged in and have permissions to create an organization.

  2. Test Case #2

    Test Case Name: Join Existing Organization

    Test Case ID: TC002

    Type of Test: Functional

    Test Scenario: User searches for "Art Club" and clicks on 'Join'.

    Test Data: User ID: "user123"

    Expected Result: The system should successfully add the user to the "Art Club" and confirm via a notification.

    Entry Criteria: User must be logged in and the organization must be open for new members.

  3. Test Case #3

    Test Case Name: RSVP to Event

    Test Case ID: TC003

    Type of Test: Functional

    Test Scenario: User navigates to the event page and clicks on 'RSVP'.

    Test Data: Event ID: "ev123"

    Expected Result: A confirmation screen appears, indicating the user has RSVP'd successfully.

    Entry Criteria: The user must be logged in, and the event must be accepting RSVPs.

  4. Test Case #4

    Test Case Name: Create an Event

    Test Case ID: TC004

    Type of Test: Functional

    Test Scenario: User fills out the 'Create Event' form.

    Test Data: Event Name: "Career Fair", Date: "2023-05-24"

    Expected Result: The event should be created, and a confirmation message should be displayed.

    Entry Criteria: User must be logged in and have permissions to create an event.

  5. Test Case #5

    Test Case Name: Search for Organizations

    Test Case ID: TC005

    Type of Test: Functional

    Test Scenario: User searches for organizations by keyword.

    Test Data: Search Term: "Club"

    Expected Result: The system returns a list of organizations matching the search criteria.

    Entry Criteria: User must be logged in.

  6. Test Case #6

    Test Case Name: Edit Organization Details

    Test Case ID: TC006

    Type of Test: Functional

    Test Scenario: Admin user edits the organization details.

    Test Data: New Description: "Updated description"

    Expected Result: The system updates the organization details and confirms the changes.

    Entry Criteria: User must be an admin and logged in.

  7. Test Case #7

    Test Case Name: View Past Events

    Test Case ID: TC007

    Type of Test: Functional

    Test Scenario: User navigates to view past events of a specific organization.

    Test Data: Organization ID: "org123"

    Expected Result: The system displays a list of past events for the selected organization.

    Entry Criteria: User must be logged in.

  8. Test Case #8

    Test Case Name: Rate an Event

    Test Case ID: TC008

    Type of Test: Functional

    Test Scenario: User submits a rating for an attended event.

    Test Data: Event ID: "ev123", Rating: 4

    Expected Result: The system records the rating and displays a confirmation message.

    Entry Criteria: User must be logged in and have attended the event.

  9. Test Case #9

    Test Case Name: Delete Organization

    Test Case ID: TC009

    Type of Test: Functional

    Test Scenario: Admin user deletes an organization.

    Test Data: Organization ID: "org123"

    Expected Result: The system confirms the deletion of the organization.

    Entry Criteria: User must have permissions and be logged in.

  10. Test Case #10

    Test Case Name: Check User Profile

    Test Case ID: TC010

    Type of Test: Functional

    Test Scenario: User views their profile information.

    Test Data: User ID: "user123"

    Expected Result: The system displays the correct user profile information.

    Entry Criteria: User must be logged in.

Exit Criteria

The exit criteria for this testing phase include:

  • All test cases must pass successfully.
  • No critical defects should remain unresolved.
  • All documentation (test case reports, results) must be completed and evaluated.
  • The platform must perform under acceptable load conditions during non-functional tests.

Upon successful completion of all test cases and meeting the exit criteria, the testing cycle will be deemed successful, allowing for further iterations and enhancements to the Engage platform.

References

  • Pressman, R. S., & Maxim, B. (2014). Software Engineering: A Practitioner’s Approach. McGraw-Hill Education.
  • Beck, K. (2001). Extreme Programming Explained: Embrace Change. Addison-Wesley.
  • Somerville, I. (2011). Software Engineering (9th ed.). Addison-Wesley.
  • Fowler, M., & Highsmith, J. (2001). The Agile Manifesto. Software Development, 9(8), 28-35.
  • Kaner, C., Falk, J., & Nguyen, Q. (2013). Testing Computer Software (3rd ed.). Wiley.
  • Patton, J. (2005). Software Testing. Sams Publishing.
  • Wiegers, K. E., & Beatty, J. (2013). Software Requirements (3rd ed.). Microsoft Press.
  • Gelperin, D., & Hetzel, W. P. (1988). The Growth of Software Testing. IEEE Software, 5(6), 19-25.
  • Schneidewind, N. F. (2003). Software Quality and Testing Strategies for Real-World Applications. IEEE Software, 20(4), 19-22.
  • Myers, G. J., Glenford, J. S., & Badgett, T. (2011). The Art of Software Testing (3rd ed.). Wiley.

Related Assignments