Skip to content
This repository has been archived by the owner on Jan 2, 2023. It is now read-only.

Latest commit

 

History

History
90 lines (69 loc) · 3.59 KB

testing_plan.md

File metadata and controls

90 lines (69 loc) · 3.59 KB

Testing plan

For our final assignment we have to create a testing plan for a component of choice.

Here I decided to test the auth/signup/signup.component.ts component.

Expectation that component is properly created

On creation the component contains:

  • A title containing "Sign up to Pillow!"
  • An email input field
  • A password input field with hide toggle
  • A confirm password input field with hide toggle
  • A button to create the account
  • A button to which links to the login page

Each of these parts can be individually tested.

Email field

Requirements of the email input field:

  • Cannot be empty
  • Contains a valid email address
  • Email is not already in use by someone else
  • Indicate to the user what is wrong with a message and/or colors
Test type Input Expectation
Positive validmail@mail.com Email field is valid
Negative Email field is not valid, field indicates it's required
Negative not<a#valid,mail.com Email field is not valid & an error message is shown indicating that the email address used is not valid
Negative bob@telenet.be Email field is not valid & an error message is shown to indicate that the email is in use
... More variations on inputs in the form, testing edge cases

Password fields

Requirements for the password and confirm password fields:

  • Cannot be empty
  • Password and password confirm values have to be the same
  • Indicate to the user what is wrong with a message and/or colors
  • Minimum length is 8 (6 for just firebase)
Test type Input password Input confirm password Expectation
Positive test1234 test1234 Fields are valid
Positive T_3@st1234567098 T_3@st1234567098 Fields are valid
Negative Fields are invalid
Negative test1234 123test Fields are invalid and message is shown to indicate that the passwords don't match
Negative 1234test Fields are invalid and message is shown to indicate that the passwords don't match
Negative test1 test2 Fields are invalid and message is shown to indicate that the minimum length is 8 and the passwords don't match
Negative test1 test1 Fields are invalid and message is shown to indicate that the minimum length is 8
... More variations on inputs in input fields, testing edge cases

Toggle password view button

Requirements:

  • Clicking the button toggles the view from text to password
  • Icon changes depending on state
  • Passwords start out hidden
Test type Action Expectation
Positive First click on password toggle Input field types of the password fields go from password to text (default is hidden first)
Positive Click on button when password is hidden Input field types of the password fields go from password to text
Positive Click on button when password is visible Input field types of the password fields go from text to password

Create account button

Requirements:

  • Only disabled when the form is invalid
  • On click, will create an account
  • Navigates the user to login after succesful account creation
Test type Action/input Expectation
Positive Valid form Button is enabled
Negative Invalid form Button is disabled
Positive Click on button with valid form Account is created
Negative Invalid form & click button No account is created, no click
... More specific types of input in the form

Login link button

Requirement:

  • Navigates user to login page
Test type Action Expectation
Positive Click on button Navigated to login page