TESTING PROTOCOL DETAILS

Following that, the prototype website will go through a number of tests to ensure that it meets
the majority of the client's criteria in time for the prototype's final presentation. Before
beginning the testing protocols, you must finish developing the prototype website; after that,
you must set up the system to be ready for testing.

The goal of the first step is to ensure that the website is live and working, in this case,
ensuring that all files have been transferred to the relevant server drive and that the
appropriate file permissions have been set so that the website can be accessed via the
temporary URL. It's also critical to ensure that (RDBMS) and SQL Script are completely
functional, error-free, and linked to the website via PHP code.

METHODS AND TOOLS

Once the website is up on the web servers, the major testing method would be to run it in an
internet browser, in this case Chrome and Microsoft Edge, thus it will be critical to ensure
that the website works in these browsers. Also, to ensure that the website is running with the
temporary URL issued by the web servers; otherwise, the website will not appear in any
internet browser. This type of testing involves a live user experience without access to the
system's internal workings also widely known as Blackbox Testing. Basically a everyday
user, who is not a tech savvy and doesn’t know much about the internal working goes
through each website functions and tests if the expected outcome comes.

EFFICIENCY TESTING

When testing the website, there will be other things to consider that will need to be
documented on the test table, such as how well it performs. This capability will be added to
the test table. A website that loads quickly, is a sign of efficiency. When it comes to
computing, load time is a common topic of discussion, especially when it comes to video
streaming. In that case, you don't want a website that takes a lengthy time to load because that
would be incredibly off-putting to any possible user who might visit it if it were to be pushed
 out. The site's initial load time will be timed to determine this. This will be noted in the test
table's remarks in connection to the website's first loading, and for clarity, the test will be
performed on all three of the specified web browsers, Google Chrome, Microsoft Internet
Explorer, and Mozilla Firefox.

Method Under
Case Input Expected Output/Effect Outcome Tester Notes
Review
Launch Website User types in
Website home page
1.1 from Google URL into Positive Site load time from URL timed at 0.92 seconds
appears
Chrome address bar
Launch Website User types
Website home page
1.2 from Microsoft URL into Positive Site load time from URL timed at 1.06 seconds
appears
Edge address bar
User types
Launch Website Website home page
1.3 URL into Positive Site load rime from URL timed at 0.89 seconds
on Firefox appears
address bar
Website home page
Website Matches User types in Website launches with full GUI and in selected
appears in chosen logo
1.4 Chosen Corporate URL into Positive corporate identity of Dark Blue, White and
and corporate colours of
Identity address bar Red
Dark Blue, Red & White

2. TEST CASE - USER & Admin LOGIN PAGES TESTS: 6

User able to use
User clicks company User to be returned User returned to home page to the
2.1 company logo to Positive
logo at top of menu bar to Home Page default top of the page
return to home page
User clicks "Login"
User Gets Error User Is taken to an Error screen displays with button to
2.2 button with no text Positive
Message for no input error screen return user to the User Login page
input
User Gets Error User clicks "Login"
Message for incorrect with user inputs that do User Is taken to an
2.3 Positive Login details must match the fields
login details on "User not comply with SQL error screen
Login" constraints
User Gets Error User clicks "Login"
Message for incorrect with user inputs that do User Is taken to an
2.4 Positive Login details must match the fields
login details on " not comply with SQL error screen
Client Login" constraints
Upon clicking the
User Inputs correct User inputs correct
"Login" button, the
2.5 login details on "User login details relevant to Positive Login details must match fields.
user is taken to the
Login" them
Homepage
2.6 Access to User inputs correct User is taken to the Positive Login details must match fields.
Administrator section login details on "User administrator
of website Login" that are portion of the
 relevant to the
website
Administrator

3. TEST CASE – USER REGISTRATION PAGES TESTS: 2

User is redirected to
User on "Sign Up" User clicks "Sign Up" User from this is able to log into the
3.1 registration is Positive
inputs form correctly with form completed system via the "User Login" page
successful page
User on"Sign UP"
User clicks "Sign Up" User sees a error User from this is able to log into the
3.2 inputs form Positive
with form completed message system via the "Client Login" page
incorrectly
4. TEST CASE Video Page TESTS: 4
Cas
Method Under Expected
e Input Outcome Tester Notes
Review Output/Effect
No'
Video page opens Requires
User gets to watch User clicks a watch live
4.1 and start playing Improvemen The livestream must
the live video video
the video t
User Gets to
User clicks a comment The comment gets
4.2 Comment on the Positive The video will be saved i
icon saved.
Video
The video gets
User gets to Save the
4.3 User clicks a save icon. saved in the Positive The comment will be save
video in archive
archive section
The event gets Requires
User gets to set a User clicks a reminder
4.4 registered for Improvemen The reminder will be save
reminder button.
reminder t