EPIC: 3.x roadmap

[AlexSkrypnyk]

• [ ] Add the step definition creation rules to the README.md (see the comment below).
• [ ] Reconcile all step definitions format to follow industry best practices (need a link here)
• [ ] Reconcile traits with the latest version of Drupal Extension to remove duplicating functionality
• [ ] Prepend Drupal trait names with Drupal and add drupal prefix to all functons
• [ ] Provide behat context as a wrapper for Traits for those users who want a turn-key solution
• [ ] Add Drupal 11 fixture and CI build

[AlexSkrypnyk]

Steps reconciliation spreadsheet:
https://docs.google.com/spreadsheets/d/11zTWgbRdTIMaXBkwli9qiZINqxxBDuKq9BhpT9iPBok/edit?usp=sharing

Add the following rules to the README.md:

• Given
  • Use exists, have
  • Try avoid using I
• When
  • Use I <verb>
• Then
  • Start with a "thing" you are asserting for
  • Do not use I
• All:
  • Use the following for tabled content
  • Anything identified by a property should use with. I.e., Then the link :link with the title :title exists.
  • Avoid "on the page" suffix - we are already on the page
  • Do not use optional words like "(the|a)" and instead provide a single form. This helps with consistency.
  • Avoid regexes in step definition comments. Use tuple format instead. It is easier to understand and maintain.
  • Use expanded names for the tuple placeholders: term_name instead of name. This allows to understand what is required faster.