larrybolt / ucll-scalatest

UCLL-ScalaTest

Story 1

Narrative:
In order to limit access to the application
As an administrator
I want to register users

# Specification 1
Scenario: the personal details of a user can be registered
Given the firstname Bert, lastname Bertels, email [email protected] and password PasswordForBert
When I choose to create the person with the given data
Then a person object is created with these data

# Specification 2
Scenario: the firstname of a user is not mandatory
Given the lastname Bertels, email [email protected] and password PasswordForBert but no firstname
When I choose to create the person with the given data
Then a person object is created with these data and no firstname

Scenario: the lastname of a user is not mandatory
Given the firstname Bert, email [email protected] and password PasswordForBert of a person but no lastname
When I choose to create the person with the given data
Then a person object is created with these data and no lastname

# Specification 3
Scenario: the password cannot be stored as plain text
Given the password PasswordForBert
When I choose to create a person with this password
Then the password is stored as a digest of 40 characters

Scenario: different passwords have different hashed values
Given the password PasswordForBert
And another password OtherPasswordForJan
When I choose to create a person with the first password
And I choose to create a person with the second password
Then the stored password of the first person is different from the stored password of the second user

Scenario: identical passwords have different hashed values
Given the password PasswordForBert
When I choose to create a person with this password
And I choose to create another person with this password
Then the stored password of the first person is different from the stored password of the second user

# Specification 4
Scenario: the email of a user is mandatory
Given the firstname Bert, lastname Bertels and password PasswordForBert but no email 
When I choose to create the person with the given data
Then an error is given
And the person is not created

Scenario: the password of a user is mandatory
Given the firstname Bert, lastname Bertels and email [email protected] but no password
When I choose to create the person with the given data
Then an error is given
And the person is not created

# Specification 5A
Scenario: the email of a user should be a valid email address
Given an email addres <email>
When I choose to create a person with this email
Then a person object is created with the given email

Examples:
| email | motivation |
| [email protected] | the local part can have one part |
| [email protected] | the local and domain part can have two parts seperated by a dot |
| [email protected] | the domain part can have three parts seperated by a dot |
| [email protected] | the first local part can contain upper- en lowercase characters, digits, hyphens and plus signs |
| [email protected] | the second local part can contain upper- en lowercase characters, digits and hyphens |
| [email protected] | the first domain part can contain upper- en lowercase characters, digits and hyphens |
| [email protected] | the third domain part can contain upper- en lowercase characters |

# Specification 5B
Scenario: the local part of an email address can have one part
Given an email address '[email protected]'
When I choose to create a person with this email
Then a person object is created with the given email

Scenario: the local and domain part of an email address can have two parts seperated by a dot
Given an email address '[email protected]'
When I choose to create a person with this email
Then a person object is created with the given email
									
Scenario: the domain part of an email address can have three parts separated by a dot
Given an email address '[email protected]'
When I choose to create a person with this email
Then a person object is created with the given email

# Specification 5C
Scenario: the email of a user should be a valid email address
Given an email addres
When I choose to create a person with this email
Then a person object is created with the given email

Examples:
( email , motivation )
( [email protected] , the local part can have one part )
( [email protected] , the local and domain part can have two parts seperated by a dot )
( [email protected] , the domain part can have three parts seperated by a dot )
( [email protected] , the first local part can contain upper- en lowercase characters, digits, hyphens and plus signs )
( [email protected] , the second local part can contain upper- en lowercase characters, digits and hyphens )
( [email protected] , the first domain part can contain upper- en lowercase characters, digits and hyphens )
( [email protected] , the third domain part can contain upper- en lowercase characters )