Detailed Test Process and Plans Report: CS1SE16 Module, March 2020

This report provides a comprehensive overview of software testing processes and plans. It details various testing stages, including documentation, website functionality, usability, and compatibility testing. The report explains component, system, and acceptance testing, outlining their objectives and methodologies. Furthermore, it presents Gherkin code examples for specific test scenarios, such as valid/invalid login attempts, adding a new high score entry, and sanitizing user-entered text. The report emphasizes the importance of thorough testing to ensure software quality, covering aspects from user interface testing to mobile-friendly testing. The content aligns with the CS1SE16 module requirements, focusing on practical application of testing principles.

4. Test Process and Plans
4.1 Test Process [10 marks]
Documentation testing
It involved testing the documentation by analysing the various site functions that have been
defined, examining the final layout of the web system and creating the website test plan for more
testing.
The main things that are usually done at this stage involves The requirements, test plan, test
cases, website functionality, Traceability matrix
Website functionality testing
It shows what the system does. It ensures every function of the website works in accordance with
the requirement specification. It involves
Links testing that verifies the Outbound links, no link is leading to the same page, correct
internal links, no broken links, if there are non referenced pages, all the links that are used to
send e-mails to site admins.
Forms testing for all pages
This involves testing the input data, the allowed data field values, invalid input values for the
data fields, form options like deleting or editing data.
Cookies testing
Test the disablead as well as enabled cookies of the site. Ensure cookies are encrypted before
they are written on the users machine. Verify there is security when cookies are removed. Test if
the expiry time of the cookies work.
HTML/CSS Testing
The syntax errors in HTML, ensure the site is available in search machines. Ensure the sitemap is
accurate in XML and HTML format.
Usability testing
This involves testing the site with the expected users in order to identify the users ability to
understand to operate, input data and interpret outputs. This is achieved through
Navigation testing
Ensuring all the pages are easy to use and understandable, the shapes, buttons and fields are easy
to use, access to the main menu from all pages
Content testing
Proper placing and sizes of images. No grammar and spelling mistakes. Ensure the color palette
and font size are optimized. The content should be understandable, linked logically, informative.
Correct information with clear instructions
UI (User Interface) testing
Ensure it conforms to the graphical interface standards. The colors, font size, layout, captions,
text formatting, links, labels, text documents. Works in various screen resolutions. Length of
names against the interface element.

Compatibility (Configuration) testing
Compatibility (Configuration) testing is performed to test your website with each one of the
supported software and hardware configurations:
OS Configuration
Cross browser compatibility (Google Chrome, Internet Explorer, Mozilla Firefox and Opera)
Database Configurations that can allow the site to work with various databases.
Printing compatibility that is the fonts, page graphics, page alignment can be printed properly
and all pages fit the paper size and the size defined in the printing option.
Performance testing
Test if the sites can withstand high loads through Load testing its behavior at increasing
workload , Stability testing Its ability to work within or above the acceptable period. Stress
testing it at or beyond the limit of its workload limit. , Endurance testing if additional workload
is given repeatedly. Volume testing through increasing the data in the database. Concurrency
testing when multiple users login to the site.
Security testing
Ensure inability of unauthorized access to secure pages .Verify that the sessions are killed
automatically after prolonged user inactivity. Ensure the SSL security is functional. Store
all attempts at breaking, through reporting errors that should be logged and stored in a separate
file. Test captcha using automatic scripts. Ensure permission before downloading restricted files.
No login when a wrong username or password is entered.
Change related testing
Run test cases that originally detected the bugs a couple of times ensuring they pass without any
problems.
Conduct Regression testing to Ensuring new defects have not appeared after the changes Check
all functionalities of your site.
Mobile-friendly testing
Quite a number People use only their mobile devices for Internet access that is why it is
important to ensure a website is mobile-friendly by testing the compatibility with smartphones
and tablets. Ensure simple site navigation. Optimize the site loading time , large buttons for
users with huge fingers, Avoid flash and pop-ups. Use short sentences and bullers, position
phone numbers in a position that is a click away. Ensure the website can access user location
through GPS.

Beta testing
It is done by the end user and non staff. It ishe final prerelease stage of testing. The real users
identify any weak points from their point of view.
4.2 Component testing [10 marks]
This is used to identify bugs and ensure the functionality of the modules that are tested
separately.
The test cases for component testing are validated against test requirements, use cases.
Component Testing in Small
It is conducted with or without isolation of the other components in the application under test. If
it's performed with the isolation of other component
A sample of a component test case for Login Module.
The login page is one component, the home page is another.
The Component testing scenario's on on the login page would be –
● Enter invalid user id and verify if the user will see user-friendly warning pop up
● Enter invalid user id and password then click on 'reset' link then verify if the data entered
in the text fields will clear out
● Enter the the correct user name and password and click on 'Login' button.
Component testing scenario's on home page –
● Verify if the "Welcome ‘username’" message is shown in the home page.
● Test if all the link on the left side of the web page are clickable.
4.3 System testing [10 marks]
This validates the complete and fully integrated sitet. It evaluates the end-to-end system
specifications.
Testing every input in the application to check if desired outputs are obtained.
Testing of the user's experience when interacting with the site.
4.4 Acceptance testing [10 marks]
It is used to determine whether the software system has met the requirement specifications.
Evaluate the system's compliance with the business requirements and verify if it is has met the
required criteria for delivery to end users by assess whether it is acceptable for delivery..
The forms of acceptance testing are
User acceptance
Verify if it is working for the user who the product is intended correctly to meet their specific
requirements.
Business acceptance

Evaluate the site if it meets the business goals and purposes . It focuses on business benefits
Alpha testing
Evaluate the site by a specialized testers team called alpha testers. Whose feedback, suggestions
help to improve the site usage and also to fix certain bugs. testing happens in a controlled
manner.
Beta testing.
The product is assessed by the real end-users called beta testers/beta users Continuous feedback
is gathered and raised issues are fixed. It helps in enhancing/improving the site to give a rich
user experience.
5. Test cases
Include your Gherkin code for three (3) specific tests (you do not need to worry about how these
tests will be implemented in executable code).
1) Tests for a valid/invalid login attempts [10 marks]
Scenario: User valid Login
Given that the user has registered in the application
And the user put username "admin" and password "1234"
When the user enter username "admin" password “1234” as the password
And the request "/login"
Then the user is successfully login
And the response body includes '{message:"Successful Login"}'
Scenario: User Invalid login
Given that the user registered in the system
And correct username is “admin” correct password “123456”
And you user puts incorrect password “admin”
When user enter the username “admin” password “admin”
And in the request is “/login”
And the password “admin” does not match the stored password “1234”
Then the error body included “details:”Incorrect Username/password”
2) Tests for adding a new high score entry [10 marks]
Scenario: Adding a new high score

Given the game ends
And the <new_score> is greater that the <highest_score> value
Then the <highest_score> value will be the value for this <new_score>
3) Tests for sanitising user entered text
Scenario: user registers in the system
Given the user fills in the registration form
And the user puts the <username> as text
And the <email address> with special characters “@”
And the <password> with one special character, one uppercase letter, one number
And the user confirms password by putting the same password <password>
When the user submits the registration form details
And the request is /register
Then the response body includes '{message:"Successful Register"}'
[10 marks]