1.

Rationale:

• Aims/Benefits of the Micro-Project:

o To study the concept of Online Event management system.

o To study how test cases are designed
o To study what test cases are designed Online event management system.

• Streamline Event Management Processes: Simplify and

automate the tasks involved in planning, organizing, and executing events
to reduce manual workload and errors.
• Enhance User Experience: Provide a seamless and intuitive
interface for both organizers and attendees, ensuring ease of use and
accessibility.
• Centralize Event Operations: Create a unified platform for
managing all aspects of an event, such as registration, ticketing, scheduling,
and communication.
• Increase Event Reach and Engagement: Enable organizers to
reach a broader audience through online platforms and interactive
engagement tools.
• Facilitate Data-Driven Decision-Making: Offer robust analytics
and reporting features to help organizers evaluate event performance and
improve future events.
• Ensure Security and Privacy: Safeguard sensitive attendee
information and payment data through robust security protocols and
compliance with data protection regulations.
• Support Hybrid and Virtual Events: Provide features tailored for
online or hybrid event formats, accommodating the growing demand for
remote participation.

pg. 1
 2.Literature Review:

• https://www.guru99.com/test-case.html
• https://www.guru99.com/what-everybody-ought-to-know-about-test-
planing.html

• Growth of Online Platforms: The adoption of digital solutions for

event management is driven by advancements in cloud computing, mobile
technology, and user-friendly interfaces. These platforms cater to various
event types, including conferences, concerts, webinars, and weddings.
• Benefits of OEMS:
o Automation: Automating tasks such as registration, reminders, and
ticket issuance reduces manual effort and errors.
o Customization: Modern systems offer customizable features to suit the
specific needs of different events.
o Scalability: These platforms handle events of varying sizes, ensuring
smooth operations regardless of the scale.
o Data-driven Insights: Analytics dashboards help organizers understand
attendee behaviors, preferences, and engagement levels.
• Challenges:
o Security and Privacy: Data protection remains a critical concern due to
the sensitive nature of attendee information.
o Usability Issues: Ensuring user-friendliness for both organizers and
participants is crucial for adoption.
o Integration: Compatibility with third-party tools and systems (e.g.,
CRM software, social media) is essential.
• Key Studies:
o Studies indicate that hybrid events (combining in-person and virtual
elements) are a growing trend, and OEMS are evolving to accommodate
such formats.
o Research highlights that real-time engagement tools like live polls, Q&A
sessions, and chat functionalities enhance attendee satisfaction in virtual
events.
•

pg. 2
 3.Course Outcomes Addressed:

▪ Apply various software testing methods.

▪ Prepare test cases for different types and levels of testing.

▪ Identify bugs to create defect report of give application

• Understand Event Management Tools: Learn to use software for

event planning, registration, and ticketing.
• Enhance Attendee Experience: Apply features like live engagement
tools and personalized schedules.
• Analyze Event Data: Generate and interpret reports to measure success
and improve future events.
• Ensure Security and Privacy: Implement best practices to protect
attendee data and comply with regulations.
• Plan and Execute Events: Organize seamless events, including virtual,
hybrid, and in-person formats.
• Adapt to Trends: Stay updated with innovative technologies in event
management.

pg. 3
➢ Actual Methodology Followed:

• Selected the topic for our microproject.

• Created the all data required for microproject.
• Studied the different test cases.
• Studied the test report also test plans.
• Prepared final report

Sr Name of Specifications Qty Remarks

No. Resource/material

1. Computer System DELL/ 1

Windows 10

Software MS Word 1

2.

pg. 4
 4.Introduction:

The main objective of this test plan is to test the Features and
Functionalities of Online. Event Management System. And to create a
proper documentation of the testing approach, schedule required for the
completion of testing, Scope, roles and responsibilities for testing, test
deliverables and the resources used for this system.

1. In Scope:
The features that are to be tested are:
❖ Home Page: The end user can access the family events and hall events
page from Home Page

➢ 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
• Culturals - 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

pg. 5
 5.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 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.

2 Test Engineers/QA ▪ To read all the documents and understand what

testers/QC testers 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

pg. 6
 6.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
outputs should be tested.
▪ Beta Testing : In Beta Testing, testing should be performed by the end user
in the real and working environment.
▪ GUI Testing : 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.

Task Members Estimate

Report Test
Test Designer 3 man-hours

Create the test Tester, Test Administrator

specification 3 man-hours

Tester
Perform Test Execution 4 man-hours

Test Delivery Tester

1 man-hours

Total
11 Man Hours
7.Project task and estimation and schedule :

pg. 7
 ➢ Test Deliverables :

o Test deliverables are provided as below: o Test Strategy. o Test Plan and
Estimation.
o Test Cases• o Test Data. o Requirement Traceability Matrix. o Test
Summary Report.
o Test Closure Report.

o Test Incident Report.

Resource & Environment Needs :

Testing Tools :

No. Resources Descriptions

1 Computer System Computer system with
latest operating system
2 Online event management Event management system
system in CSS

8.Test cases on Online Event Management System:

pg. 8
Test cases ID Scenario Pre Test Data Test Steps Expected Actual result Test
Conditio Result Result
ns

TC_1 input of Name: 1) Click We Name Pass

Validat the Riya on name proceed entered
e name name textbox to f ill successfully
text should 2) Enter email id and
box by be correct proceed for
correct enabled. name email id
name

TC_2 Validate Text box Name:1 1)Click Alert Alert Pass

name should 23@3 on name message message is
text box be textbox as “Enter displayed
by enabled 2)Enter characters as “Enter
incorrec incorrect only!” characters
t name name should be only!”
given
TC_3 Validate Text box - 1)Click Alert Alert Pass
name should on name message message is
text box be textbox as “Please displayed
by enabled 2)Don’t enter as “Please
without enter the your enter your
entering name name!” name!”
name should be
given

TC_4 Validate Text box riyasaw 1)Click Email id Email id f Pass

email should ant@g on email should be illed
text box be mail.co id f illed successfull
by enabled textbox y
correct 2)Enter
email id correct
email id

TC_5 Validate Text box Riyasaw 1)Click Alert Alert Pass

email of email ant123g on email message message
text box id mail.co id as “Enter displayed
by should m textbox valid as“ Enter

pg. 9
 incorrec be 2)Enter email id!” valid email
t email enabled incorrect should be id!”
id email id given

TC_6 Validate Text box - 1)Click Alert Alert Pass

Email of email on message message
Terabox id email as “Please displayed
Without Should id Enter as “Please
Entering be textbox your Enter your
Email id enabled 2)Don’t email id!” email id!”
email id should be
given

pg. 10
➢ Skill Developed

1. Designing test cases for applications/websites

2. Efficient communication skills.
3. Working as a team.
4. Developing leadership qualities.

➢ Application of this Micro-Project:

To check validations in your application and websites and find out the
defects and correct it.

pg. 11
9.Conclusion:
The Online Event Management System (OEMS) simplifies event planning
and management with features like user authentication, event creation,
booking, and payment integration. By designing comprehensive test cases,
we ensured the system’s functionality, security, and performance. The
testing process validated its reliability, user-friendliness, and scalability,
making it a robust solution for diverse event management needs.

pg. 12
10.References:
https://www.geeksforgeeks.org/ https://www.w3schools.com/

https://www.softwaretestinghelp.com/

pg. 13