Scribd
Upload
23 views3 pages

Software Requirement For Laravel Web Page

Uploaded by

Mehul Maheshwari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views3 pages

Software Requirement For Laravel Web Page

Uploaded by

Mehul Maheshwari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Software requirement for Laravel Web page:

(A simple webpage for registering and logging in Users based on the credentials
and show some basic information dynamically) The application will contain
various webpages like Registration page, Logging in Page, Dashboard, Add new
Users, Edit Existing User, etc. The objective of this web app is to understand how
different elements work in real time on an app and learn how to work with CSS
selectors on the long run and be able to manipulate them while trying to do manual
and automated website testing. All of the data is being stored locally on a database
hosted on XAMP MySQL.

Different elements of the web app:


1. Registration Page

1.1.Input fields for data like name, username, email address, phone number,
password, etc. are required.
1.2.Select fields for getting the Location of the user statically and dynamically.
1.3.Various buttons to redirect the user from one page to another and button to
submit the form.
Once a user has input all the necessary information required in the input fields
(which are mandatory) the user can click submit and a mail for confirmation is
sent to the given user email address using mailtrap.io server for testing
purposes.
2. Login Page

2.1.There are two input fields to enter your user credentials. One for username/
email address and another for password.
2.2.There are buttons to redirect to different pages and to login to your
dashboard.
Once the user enters the necessary information and hits enter, the user data is
authenticated and verified by Laravel matching them with the information
present on the database the user is logged in and redirected to the Dashboard. If
the user credentials don’t match an appropriate messaged is displayed to the
user.
3. Dashboard Page

There are various elements on the Dashboard, but the prominent ones are:
3.1.Users Data Table
A table is present on the page showing the information of all the users who
have registered and are present on the database. All users have a unique ID
that works as a primary key for MySQL and helps in differentiating the
users.
3.2.Edit Button
An option to edit user information is present to the user, when they click the
edit button, they are redirected to the edit page where all the user data can
be modified and is updated once you hit submit.
3.3.Delete Button
A delete button is present to delete the user using their unique ID when the
button is clicked.
4. Edit Page

The edit page is similar to the Registration form with small differences. It has a
similar structure and same input fields except for the password. The major
difference is that the user can see the previously entered information present on
the database already entered which can be used for reference and also be
modified. This simplifies the task of the user as they might not have the access
to modify the details directly on the database server.

Cypress:

Cypress is a front-end testing tool built for the modern web. I have been learning
how to use it on the latest version and will try to implement it for testing the
company’s various applications to make the work easier, decreasing the testing
time and reducing the load. Cypress is a framework which communicates with the
browser and performs certain actions depending on the code written. If I want to
test an XYZ.com website I can type the code to visit the website perform certain
actions and check for some assertions to verify if the site is working and decrease
the manual load on the various testers and increase efficiency by being able to re-
use the code.

You might also like