Skip to main content
edited tags
Link
Chris Kenst
  • 3.7k
  • 23
  • 43
Tweeted twitter.com/StackSQA/status/1028974877934530560
edited title
Link
Michael Durrant
  • 25.2k
  • 3
  • 41
  • 113

Test case How to design doubttest cases for phone number and email input fields?

Bumped by Community user
Bumped by Community user
added 34 characters in body
Source Link
mzevenkay
  • 73
  • 1
  • 2
  • 6

I'm trying to improve the design of test cases but I came across a different approach from some partners. For example, let's say there's a form to test, this form has 2 fields (phone and email) and a submit button.

My approach:

Positive flow:

  • TC1: Submit with all valid fields

Negative functionality:

  • TC2: submit with all valid fields but phone empty
  • TC3: submit with all valid fields but phone with letters
  • TC4: submit with all valid fields but phone with symbols
  • TC5: submit with all valid fields but phone with unicode chars
  • TC6: submit with all valid fields but phone with 1 number (boundary)
  • TC7: submit with all valid fields but phone with 11 charsnumbers (boundary) and so on
  • TC8: submit with all valid fields but email with 2 @s
  • TC9: submit with all valid fields but email without top level domain
  • TC10: submit with all valid fields but email with 2 dots in domain name
  • TC11: submit with all valid fields but email empty
  • TC12: submit with all valid fields but email without domain and so on

My partner's approach:

Positive functionality:

  • TC1: submit with all valid fields

Negative functionality:

  • TC2: submit with all valid fields but phone is tested in every step
    (covering my previous test cases: empty, letters, chars, etc)
  • TC3: submit with all valid fields but email is tested in every step (covering my previous test cases: empty, domain empty, etc)

What's your opinion about these approaches? Take into consideration that these test cases must be automated as well. What are the pros and cons?

Last but not least, another doubt, is it necessary to add styles verification in the steps?

For Example:

  • Step: Verifiy the title is bold and aligned left
  • Step: Hover the link - Expected Result: Link turns blue.

Thank you in advance.

I'm trying to improve the design of test cases but I came across a different approach from some partners. For example, let's say there's a form to test, this form has 2 fields (phone and email) and a submit button.

My approach:

Positive flow:

  • TC1: Submit with all valid fields

Negative functionality:

  • TC2: submit with all valid fields but phone empty
  • TC3: submit with all valid fields but phone with letters
  • TC4: submit with all valid fields but phone with symbols
  • TC5: submit with all valid fields but phone with unicode chars
  • TC6: submit with all valid fields but phone with 1 number
  • TC7: submit with all valid fields but phone with 11 chars
  • TC8: submit with all valid fields but email with 2 @s
  • TC9: submit with all valid fields but email without top level domain
  • TC10: submit with all valid fields but email with 2 dots in domain name
  • TC11: submit with all valid fields but email empty
  • TC12: submit with all valid fields but email without domain and so on

My partner's approach:

Positive functionality:

  • TC1: submit with all valid fields

Negative functionality:

  • TC2: submit with all valid fields but phone is tested in every step
    (covering my previous test cases: empty, letters, chars, etc)
  • TC3: submit with all valid fields but email is tested in every step (covering my previous test cases: empty, domain empty, etc)

What's your opinion about these approaches? Take into consideration that these test cases must be automated as well. What are the pros and cons?

Last but not least, another doubt, is it necessary to add styles verification in the steps?

For Example:

  • Step: Verifiy the title is bold and aligned left
  • Step: Hover the link - Expected Result: Link turns blue.

Thank you in advance.

I'm trying to improve the design of test cases but I came across a different approach from some partners. For example, let's say there's a form to test, this form has 2 fields (phone and email) and a submit button.

My approach:

Positive flow:

  • TC1: Submit with all valid fields

Negative functionality:

  • TC2: submit with all valid fields but phone empty
  • TC3: submit with all valid fields but phone with letters
  • TC4: submit with all valid fields but phone with symbols
  • TC5: submit with all valid fields but phone with unicode chars
  • TC6: submit with all valid fields but phone with 1 number (boundary)
  • TC7: submit with all valid fields but phone with 11 numbers (boundary) and so on
  • TC8: submit with all valid fields but email with 2 @s
  • TC9: submit with all valid fields but email without top level domain
  • TC10: submit with all valid fields but email with 2 dots in domain name
  • TC11: submit with all valid fields but email empty
  • TC12: submit with all valid fields but email without domain and so on

My partner's approach:

Positive functionality:

  • TC1: submit with all valid fields

Negative functionality:

  • TC2: submit with all valid fields but phone is tested in every step
    (covering my previous test cases: empty, letters, chars, etc)
  • TC3: submit with all valid fields but email is tested in every step (covering my previous test cases: empty, domain empty, etc)

What's your opinion about these approaches? Take into consideration that these test cases must be automated as well. What are the pros and cons?

Last but not least, another doubt, is it necessary to add styles verification in the steps?

For Example:

  • Step: Verifiy the title is bold and aligned left
  • Step: Hover the link - Expected Result: Link turns blue.

Thank you in advance.

Source Link
mzevenkay
  • 73
  • 1
  • 2
  • 6
Loading