Laboratorio 4

Nombres: Emily Peñaranda Anagua

Jonathan Abad Estrada
Danilo Andres Castro De la hoz
David Abad

Actividad 1
Analisis de Variables en los formularios por cada estudiante

Tabla clasica de dominio

Form:
Variable Class equivalence Valid Case INVALID CASE CASE EQUIVALENCE Limit and special cases Notes

Primary dimension
First Name Empty
Character set Test'
Length >= 1 character It does not have a maximum length
Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'

Set of numbers >=0 Accept any character - number

<=0
Secondary dimension
First Name Blanks only TAB,
Spaces between medium Name <space><space> los
Spaces at the end David <space><space>
Spaces ahead <space><space> David

Primary dimension
Last Name Empty
Character set Test'
Length >= 1 character It does not have a maximum length
 Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'

Set of numbers >=0 Accept any character - number

<=0
Secondary dimension
If it is composed only of
blank spaces, take it
Last Name Only empty spaces TAB, as if it were empty
Spaces between medium Name <space><space> los
Spaces at the end David <space><space>
Spaces ahead <space><space> David

Primary dimension
Email Address Empty
The presence of '@' and
Simple valid email: "[email protected]" The "@" symbol is missing: "userexample.com" Valid characters before
Email with subdomain: "[email protected]" Faulting domain: "User @com" Length >= 1 character
Email with numerical characters: "[email protected]" LOCAL PART: "@Example.com" ' !,@,#,$,%,^,&,*,(,),_,' + @ + dominio
Email with points in the local part: "[email protected]" LOCAL PART: "@Example.com"
Secondary dimension
If it is composed only of
blank spaces, take it
Email Address Only empty spaces as if it were empty
Spaces between medium
Spaces at the end
Spaces ahead

Primary dimension
Country
Afghanistan,
Aland Islands,
Albania
Algeria
American Samoa
Andorra
Angola
Anguilla
Antarctica
Antigua And Barbuda
Argentina
Armenia
Aruba
Australia
Austria
Azerbaijan
Bahamas
Bangladesh
Barbados
Belarus
Belgium
Belize
Benin
Bermuda
Bhutan
Bolivia
Bosnia And Herzegovina
Botswana
Brazil
British Indian Ocean Territory
Brunei Darussalam
Bulgaria
Burkina Faso
Cambodia
Cameroon
Canada
Canary Islands
Cape Verde
Cayman Islands
Central African Republic
Chad
Chile
China
Christmas Island
Cocos (Keeling) Islands
Colombia
Comoros
Congo
Congo, Democratic Republic
Cook Islands
Costa Rica
Cote D'Ivoire
Croatia
Cuba
Curacao
Cyprus
Czech Republic
Denmark
Djibouti
Dominica
Dominican Republic
Ecuador
Egypt
 If it is composed only of
blanks, take it
as if it were empty

Secondary dimension
Country
Selection of a country from the options list No selection of a country from the options list The user must select at least one country

Primary dimension
Company Name Vacio It's not an obligatory field
Character set 'Test Company Name'
Longitud >= 1 caracter It does not have a maximum length
Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'

Set of numbers >= 0 Accept any character - number

<= 0
Secondary dimension
Company Name Only blank spaces TAB, un espacio
Spaces between medium Company <espacio><espacio> Name
Spaces at the end CompanyName<espacio><espacio>
Spaces ahead <espacio><espacio>CompanyName

Primary dimension
Phone Number Empty
Set of numbers >=0
It does not have a maximum length
Longitud >= 1 nor with an adequate minimal length
Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'
Scripts between numbers ' 75686767 - 0000 - 000 '

Secondary dimension
If it is composed only of
blank spaces, take it
Phone Number Only blank spaces TAB, un espacio as if it were empty
Spaces between medium 7568 <espacio><espacio> 6767
Spaces at the end 75686767<espacio><espacio>
Spaces ahead <espacio><espacio>75686767
Code of Country in front ' +591 75686767 '
Decimal number 756867,67
 Primary dimension
Address 1 Empty
Character set 'Address 1'
Longitud >= 1 caracter It does not have a maximum length
Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'

Set of numbers >= 0 Accept any character - number

<= 0
Secondary dimension
If it is composed only of
blank spaces, take it
Address 1 Only blank spaces TAB, un espacio as if it were empty
Spaces between medium Add <espacio><espacio> ress1
Spaces at the end Address1<espacio><espacio>
Spaces ahead <espacio><espacio>Address1

Primary dimension
Address 2 Vacio No es un campo obligatorio
Conjunto de caracteres 'Address 2'
Longitud >= 1 caracter No cuenta con una longitud maxima
Conjunto de caracteres especiales ' !,@,#,$,%,^,&,*,(,),_, ......'

Conjunto de numeros >= 0 Acepta cualquier caracter - numero

<= 0
Secondary dimension
Address 2 Solo espacios en blanco TAB, un espacio
Espacios entre medio Add <espacio><espacio> ress2
Espacios al final Address2<espacio><espacio>
Espacios por delante <espacio><espacio>Address2

Primary Dimension
Existing Oldpassword123@ =
password It's the same as the password you have in use Oldpassword123@
It's not the same as the password you have Oldpassword123@ ≠
in use NotOldpassword123@
OldPassword123@ ≠
password Not the same as the old password NewPassword123@
It's the same as the password you have in Oldpassword123@ =
use Oldpassword123@
<8 characters letter
>=8 characters Secure1@
 Secure11234@5
<=20 characters Securepassword67776@
>20 characters Securepassword67776@
Mix of uppercase, lowercase, and symbols Password123@
Lowercase only password
solo mayusculas PASSWORD
Confirm new "Password123@"="
Password it's the same as the new password Password123@"
"Password123@"≠"
it's Not the same as the new password Pass123@"
Secondary Dimension
password Contains no spaces SecurePassword1234%
Contains spaces before, after, or between
characters SecurePassword123@
SecurePassword123@
Secure Password132@
At least one special character Secure1245@
sEcure123@@@
SecurePasswordForMyAcco
No special character unt123456

Primary dimension
Zip Code Empty It's not an obligatory field
Character set 'Zip Code'
Longitud >= 1 caracter It does not have a maximum length
Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'

Set of numbers >= 0 Accept any character - number

<= 0
Secondary dimension
Zip Code Only blank spaces TAB, un espacio
Spaces between medium Zip <espacio><espacio> Code
Spaces at the end ZipCode<espacio><espacio>
Spaces ahead <espacio><espacio>ZipCode

Primary dimension
City Empty
Character set 'City Name'
Longitud >= 1 caracter It does not have a maximum length
Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'
 Set of numbers >= 0 Accept any character - number
<= 0
Secondary dimension
If it is composed only of
blank spaces, take it
City Only blank spaces TAB, un espacio as if it were empty
Spaces between medium City <espacio><espacio> Name
Spaces at the end CityName<espacio><espacio>
Spaces ahead <espacio><espacio>CityName

Primary dimension
State/Region Empty
Character set 'City Name'
Longitud >= 1 caracter It does not have a maximum length
Special characters set ' !,@,#,$,%,^,&,*,(,),_, ......'

Set of numbers >= 0 Accept any character - number

<= 0
Secondary dimension
State/Region Only blank spaces TAB, un espacio
Spaces between medium State<espacio><espacio> Region
Spaces at the end State/Region<espacio><espacio>
Spaces ahead <espacio><espacio>State/Region

Email (email):

Variable: It is an entry field that requires validation to ensure that it meets the proper format of an email address.
Dimensions:
Primary: It was divided into valid and invalid cases to cover a wide range of possible formats and email address structures.
Secondary: The length of both the local part (local part) and the domain was considered to ensure that the validation is robust and capable of handling different lengths.
Class equivalence:
Valid cases that represent various formats and email address structures that meet the standards are identified.
Invalid cases were also identified that cover common error situations, such as the lack of "@" symbol or characters not allowed.
The limits were established to represent both the minimum and the maximum allowed within a valid email field.

Firstname (name):

Variable: Represents the name of a user or entity.

Dimensions:
Primary: It focused on the length of the name to ensure that the validation is adequate for different entry lengths.
Class equivalence:
Valid cases were identified that represent short, moderate, long but valid, and very long names, which cover a wide variety of possible names.
Invalid cases were also identified that cover common error situations, such as empty names or names that exceed a maximum length.
The limits were established to represent both the minimum and the maximum allowed for a valid name.

Lastname (last name):

Variable: Represents the surname of a user or entity.
Dimensions:
Primary: focuses on the length of the last name to ensure that the validation is adequate for different entry lengths.
Firstname (name):

Variable: Represents the name of a user or entity.

Dimensions:
Primary: It focused on the length of the name to ensure that the validation is adequate for different entry lengths.
Class equivalence:
Valid cases were identified that represent short, moderate, long but valid, and very long names, which cover a wide variety of possible names.
Invalid cases were also identified that cover common error situations, such as empty names or names that exceed a maximum length.
The limits were established to represent both the minimum and the maximum allowed for a valid name.

Lastname (last name):

Variable: Represents the surname of a user or entity.
Dimensions:
Primary: focuses on the length of the last name to ensure that the validation is adequate for different entry lengths.
Class equivalence:
Valid cases would be identified that cover short, moderate, long but valid and very long surnames, representing a variety of possible surnames.
Invalid cases would be identified that cover common error situations, such as empty surnames or exceeding a maximum length.
Limits to represent both the minimum and the maximum allowed for a valid surname would be established.
 Actividad 2
LLTC de los casos anteriormente analizados

Low Level Test Cases

Escala de Prioridad
1 2 3 4 5
Muy alta Alta Media Baja Muy Baja

Author Emily Peñaranda Anagua

Verify that the addres email does not contain spaces Edit the
Title
account of an already registered user
This test seeks to verify that the email does not allow spaces when
Description
editing the email of an existing user
Priority 1
Having access to the internet
Have chrome installed
Requirements
Have access phptravels.org
Have an active account on phptravels.org
Steps Expected result
1. Log in to the active account The Home screen should be displayed
2. Click on the "update" button The Home screen should be displayed
3. Click on the "Email Address"
text area to change the email The text of the email address must be editable
4. Write the new email with
spaces The text should be displayed in the text area
5. Click Save Changes The page should be refreshed by loading the data of the new email,
showing the message "Changes Saved Successfully!"
El usuario deberia actualizarse.
EL siguiente request deberia mandarse al API:
Endpoint:
:authority:
phptravels.org
:method:
GET
:path:
/assets/js/StatesDropdown.js
:scheme:
https
Accept:
*/*
Accept-Encoding:
gzip, deflate, br, zstd
Accept-Language:
en-US,en;q=0.9,es;q=0.8
Cache-Control:
no-cache
Cookie:
WHMCSlogin_auth_tk=d0NxZHBVTGl6cG0yeERVVWQ5MFBFRkJ3M
XJvK1U1UEg5RmVTbGlHcGJwWnJNL3ZaSkJiY0Y4STdLOHA3SUJkekN
CVXZwalUxOXJWenlpVjhWcGloVE9JY2hLaXNDZGMvYWlLOUx0bDV
OZUFGL3VJNUx6ZVAyYTlmM0U1bTBNako0c09idkhPTUUxOUZFTVR
4UEZlT2lJeHM3Zi9oWjlpcVM1b0hxVXY5Q2srZVB5QnBuMVZqL281d
StxdnN6am1jckRaL3Y3TnpsWUh2VzRGbDRMdjRtTGdPWTlGWWtaY
2NhcFJZNldWNUxOWjdvRmUyR0VGZHlzTHhRZDNUMC90QnYvVUp
kYWRxQjdJTHpPWFFGRUQ0U01RcjczeHN6YjVsKzI1aVJ3dUJuZU5Vb
k5OOEZISEtlRHU5dXJHSDBrRVZpK09iTnJjc2twajk5M0lIcmVscUVDb
W5qKzRwbHZtVzZuV3oxbnplTW44bnBwb1dDMWhIQ0ZuVWZONm
x1ZFZIZkF1aWd4TDJxaCtFanRaWXozTWdiMjZBRCtBNnlzS0RrRkNob
VBJPQ%3D%3D;
WHMCSnA1ODpxJY7TW=3b90d739518aebe23ec83dbb4b5e2c03
Pragma:
no-cache
Priority:
u=2
Referer:
https://phptravels.org/clientarea.php?action=details&success=1
Sec-Ch-Ua:
"Google Chrome";v="125", "Chromium";v="125", "Not.A/Brand";
 Autor Emily Peñaranda Anagua
Verify that the user can't enter special characters in the name when
Title
editing it on the Your profile page
This test is responsible for verifying that the user cannot enter
Description
special characters in the First Name space such as $#%^
Priority 1
Having access to the internet
Have chrome installed
Requirements
Have access phptravels.org
Have an active account on phptravels.org
Steps Expected result
1. Open the phptravels page The phptravels homepage should be displayed
2. Log in to the phptravels app The user's board should be displayed with the options of services,
tickers, signups and invoices.
3. Click on the 3-line button at
the top of the screen A menu should appear with a Hello [user] option
4. Click on the Hello option,[user] A new menu should be displayed with a "Your Profile" option
5. Click on the First Name text
area The text should be displayed in the text area
6 Typing the new name with data
that contains special characters It should display a warning for special characters

Title Length Limit Validation for the "Name" Field

This test aims to verify whether the system
correctly handles the length limits for the "Name"
field. Both the minimum and maximum allowed
Description limit for the name will be tested.
Priority 5
 Have access to the internet
Have chrome installed
The system must allow names with a minimum
length of one character.
The system must reject names with a length that
exceeds the maximum allowable limit.
The system should display clear and descriptive
error messages when a name is entered that does
Requirements not meet the length limits.
Límite Mínimo de Longitud:

Ingresar un nombre con una longitud de un solo

carácter (por ejemplo, "A").
Verificar si el sistema acepta el nombre y muestra
un mensaje de éxito.
Confirmar que el sistema no rechaza el nombre y
no muestra ningún mensaje de error relacionado
con la longitud.
Límite Máximo de Longitud:

Ingresar un nombre con una longitud que exceda

el límite máximo permitido (por ejemplo, un
nombre extremadamente largo).
Verificar si el sistema rechaza el nombre y muestra
un mensaje de error indicando que el nombre es
demasiado largo.
Confirmar que el sistema no permite ingresar el
nombre y que se muestra un mensaje de error
Steps adecuado.
Desing Jonathan Abad
 For the minimum length limit, the system is
expected to accept the name and display a success
message without showing length-related errors.
For the maximum length limit, the system is
expected to reject the name and display a clear
error message indicating that the length of the
Expected result name is too long.

Title Email Display Validation for the "Email" field

This test aims to ensure that the system correctly
Description displays the email address entered by the user.
Prioridad 5
"The system must display the email address
entered by the user in the proper format.
The system must allow the email address to be
displayed correctly at all points of interaction
Requeriments where it is required."
"Enter a valid email address in the appropriate
field (e.g., "[email protected]").
Check if the system displays the correctly entered
email address in the proper format.
Confirm that the email address is displayed
correctly in all parts of the system where required,
Steps such as on registration forms, user profiles, etc."
Desing Jonathan Abad
The system is expected to show the email address
entered by the user in the right format, without
visualization errors.
Email address is expected to be correctly displayed
in all parts of the system where its visualization is
required, guaranteeing a coherent and problem -
Expected result free user experience.
 Check the response of the "Subject" field by
Title sending it empty.
This test case seeks to verify the validation of the
Description "Subject" field by sending it empty.
An empty title
does not imply
a high risk for
the functionality
3 or application,
but must be
tested to ensure
consistency of
Priority functionality
Have access to the internet
Have chrome installed
Have access to phptravels for example: https:
//phptravels.org/
Have a created account registered in the
Requirements application
Steps Expected result
1. Enter the link
provided in the
requirements The phptravels login page should display.
2. Log in to the It should redirect you to the main dashboard of
application the application.
3. Click on the
"Open ticket" It should redirect you to the "Open ticket"
link functionality page.
4. Select a You should open the form to make and submit the
department. ticket.
5. Write a text
in Message, Fill
out the captcha
and send the The application should raise an alert indicating
ticket without a that a ticket with an empty subject cannot be
Subject submitted
Designer Danilo Castro
 Check the response of the functionality when
sending an attachment with an extension that is
Title not allowed.
This test case seeks to verify the validation of the
application of the attachments with respect to the
Description extensions of these attachments.
It is important to
test that the
application is
validating the
entry of only
files with the
specified
1 extensions to
avoid the entry
of malicious
files or scripts
that could put
the security of
the application
at risk.
Priority
Have access to the internet
Have chrome installed
Have access to phptravels for example: https:
//phptravels.org/
Have a created account registered in the
Steps application
Steps Expected result
1. Enter the link
provided in the
requirements The phptravels login page should display.
2. Iniciar sesión It should redirect you to the main dashboard of
en la aplicacion the application.
3. Click on the
"Open ticket" It should redirect you to the "Open ticket"
link functionality page.
4. Select a You should open the form to make and submit the
department. ticket.
5. Write a text
in the Subject
and Message
sections. Attach
a file with an
extension other
The application should raise the following alert:
than those
"The file you tried to upload is not allowed."
allowed (for
example, a .py
or an .exe). Fill
out the captcha
and send the
form.
Designer Danilo Castro

Verify the user usability of the "Change password"

Title
form in PHPTravels
This test case will verify that the user interface and
usability of the password change form in PHP
Description
travels are adequate and provide a good user
experience
Priority 4
Have access to the internet
Have a browser installed (chrome will be used for
this test)
Requeriments
Access PHPTravels path: https://phptravels.org/
Have an account created to use the app
Have an active password
steps: Expected result
1. Go to
PHPTravels The PHPTravels homepage should be displayed
website
2. Logear en la
The user's client area should be displayed with its
aplicacion de
corresponding services
PHPTravels
3. Click on the a drop-down menu should be displayed with the
drop-down following options: Account details, User
menu with text Management, Contacts, Account Security, Email
"Hello, [your history, Your profile, Change password, Security
name]" Settings, and logout
4. Click on the
"Change You should be redirected to the password change
Password" form
option
5.. Verify that
the password The form should contain three different input
change form is fields: "Existing password", "New password" and
displayed "Confirm new password"
correctly
6. Verify that
Tags should be descriptive and easy to understand
input fields
(e.g., "Enter your Current Password" or "Enter a
have proper
new password")
labels
7. Verify that
input fields are It should be possible to click on each field and type
accessible and text into it
allow text input
8. Verify that
the text Text should be displayed as hidden and only show
entered into dots e.g. ******. with option to reveal text to
the fields is verify password
censored
11. Click on the
"Save Changes" You should reload the page and display a message
button at the at the top of the form with the text "Changes
bottom of the Saved Successfully
form
Estimated Time 5 min
Author Favio Calvi

Verify that the User cannot change his/her

Title password by using an insecure password in the
"Change Password" form in PHP travels
This test case is to verify that a user cannot change
their password to one that does not meet the
Description
security requirements established in the
PHPTravels application
Priority 2
Having access to the internet
Have a browser installed (chrome will be used for
this test)
Requerimientos
Access PHPTravels path: https://phptravels.org/
Have an account created to use the app
Have an active password
steps: Expected result
1. Go to
PHPTravels The PHPTravels homepage should be displayed
website
2. Logear en la
The user's client area should be displayed with its
aplicacion de
corresponding services
PHPTravels
3. Click on the a drop-down menu should be displayed with the
drop-down following options: Account details, User
menu with text Management, Contacts, Account Security, Email
"Hello, [your history, Your profile, Change password, Security
name]" Settings, and logout
4. Click on the
"Change You should be redirected to the password change
Password" form
option
5.. Click on the
text area to The cursor should be displayed at the beginning of
type Existing the Tex Area
Password
6 Enter the
current Text should be displayed as hidden and only show
password you dots Example: ******
want to change
7.. Click in the
text area to The cursor should be displayed at the beginning of
type New the text area
Password
8 Write a new
password that
does not meet
the security
requirements Text should be displayed as hidden and only show
(at least 8 dots e.g. ******. with option to reveal text to
characters, a verify password
capital letter
and a species)
example:
12345678
9.. Click on the
text area to The cursor should be displayed at the beginning of
type Confirm the Tex Area
new password
10. Re-enter
the SAME
password that Text should be displayed as hidden and only show
was entered in dots e.g. ******. with option to reveal text to
the text area of: verify password
"New
password"
11. Click on the
You should reload the page and display a message
"Save Changes"
at the beginning of the form with the text "The
button at the
password you entered is not strong enough -
bottom of the
please enter a mor complex password"
form
Estimated Time 5 min
Author Favio Calvi