Introduction:

"Designing Test Cases on Online Event Management System" is conducted under the subject of Software
Testing. The primary objective of this micro-project is to develop a set of comprehensive test cases for an
Online Event Management System. Software testing is a crucial phase in the software development lifecycle,
ensuring that the system functions as intended and meets the requirements of its users.
The primary goal of this micro-project is to enhance our understanding of software testing
methodologies and their practical application. By systematically designing test cases for the
Online Event Management System, we aim to uncover potential issues, validate system
functionality, and contribute to the overall quality assurance of the software.
This introduction sets the stage for our exploration of software testing principles and their
practical implementation in the context of the Online Event Management System. Through
this endeavor, we seek to acquire valuable insights into the world of software testing and its
crucial role in software development and quality assurance.
 Aims/Benefits of the Micro-Project

Aim:

The primary aim of this project, "Designing Test Cases on Online Event Management
System," within the realm of software testing is to:
Enhance Software Quality Assurance: The project aims to improve the quality assurance
process of the Online Event Management System by systematically designing, implementing,
and executing a comprehensive suite of test cases.

Benefits:

 To study the concept of Online Event management system.

 To study how test cases are designed
 To study what test cases are designed online event management system
 Quality Assurance Improvement
 Validation of Functionality
 Usability Enhancement
 Security Assessment
 Performance Optimization
 Documentation and Knowledge Transfer
 Industry-Relevant Experience
 Contribution to Software Testing Field

Objectives of the Project Report:

Documentation of Test Cases: Provide a comprehensive documentation of the test cases

designed for the Online Event Management System, including test scenarios, inputs, expected
results, and execution steps.
Test Execution Results: Present detailed reports of test case execution, including pass/fail
status, to provide insights into the system's behavior and identify defects.
Defect Documentation: Document identified defects, anomalies, or issues encountered during
testing, including their severity, priority, and steps to reproduce.
Performance Metrics: Share performance testing results, including response times,
throughput, and resource utilization, to assess the system's performance under different
scenario
Scope
The features that are to be tested are:

 Family Events Page - The end user can access the family events
From Family events page

 Marriage - The end user can fill their information and book
The event

 Reception - The end user can fill their information and book
The event

 Birthday Party - The end user can fill their information and
Book the event

 Cultural - The end user can fill their information and book
The event

 Hall Events: The end user can access the family events from Hall
Events page.

 Meetings: The end user can fill their information and book
The event

 New Year: The end user can fill their information and book
The event

 Office Party: The end user can fill their information and
Book the event

 Book Publish: The end user can fill their information and
Book the event

Quality Objective:

The test objectives are to verify the features and Functionalities of Online Event
Management System. The testing team should focus on testing all the options
Available on the System interface and to guarantee that all those operations can
Work accordingly in the real environment

Roles and Responsibilities:

Sr. Roles Responsibilities

No.

1 Test Manager  Defining the testing activities

2 Test Engineers/QA
testers/QC testers
for subordinates –
Testers or test engineers.
 All responsibilities of test
planning.
 To check if the team has all
the necessary resources
 To execute the testing
activities.
 To check if testing is going
hand in hand with the
 Software development in all
phases.
 Prepare the status report of
testing activities.
 Required Interactions with
customers.
 Updating project manager
regularly about the
 Progress of testing activities.
 To read all the documents and
understand what
 Needs to be tested.
 Based on the information
procured in the above
 Step decide how it is to be
tested.
 Inform the test lead about
what all resources will be
 Required for software testing.
 Develop test cases and
prioritize testing activities.
 Execute all the test case and
report defects, define
 Severity and priority for each
defect.
 Carry out regression testing
after every change in
 Test Methodology:
 Unit Testing: In unit testing all the modules should be tested individually
To check if everything is correct.
 Black box testing: In Black-box testing all combination of inputs and
 Beta Testing: In Beta Testing, testing should be performed by the end
 GUI: In GUI testing the Graphical User Interface of the software
Should be tested.

Suspension Criteria and Resumption Requirements:

If the testers report that there are 50% failed test cases then suspend the testing
Until the development team fixes all the failed cases.

Test Completeness:
 specifies the criteria that denote a successful completion of testing the
software.
 Run rate is mandatory to be 100%, unless a clear reason is given.
 Pass rate is 80%, achieving the pass rate is mandatory