Use meaningfull testcase names #1

Closed
opened 2021-09-05 12:45:08 +02:00 by Simon · 0 comments
Owner

We should avoid using test case named like "Should work as intended":

  • intended doesn't describe the specifications and can't help one to understand what is correct or not. (tacite documentation)
  • test case is loosely binded to a specification reference. Feature or UC #nnnn
  • test case doesn't describe the test topic and scope. Testing user login feature
We should avoid using test case named like "Should work as intended": * *intended* doesn't describe the specifications and can't help one to understand what is correct or not. (tacite documentation) * test case is loosely binded to a specification reference. *Feature or UC #nnnn* * test case doesn't describe the test topic and scope. *Testing user login feature*
Simon added this to the Improve the cypress project milestone 2021-09-05 12:45:08 +02:00
Simon added the
bug
label 2021-09-05 12:45:08 +02:00
Simon closed this issue 2022-06-30 00:37:03 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Trusk/Partie-3#1
No description provided.