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 functions

• Provide behat context as a wrapper for Traits for those users who want a turn-key solution

• Add Drupal 11 fixture and CI build

• 3.x Update ContentTrait #279

• 3.x Update CookieTrait #280

• 3.x Update DraggableViewsTrait #281

• 3.x Update EckTrait #282

• 3.x Update ElementTrait #283

• 3.x Update EmailTrait #284

• 3.x Update FieldTrait #285

• 3.x Update FileDownloadTrait #286

• 3.x Update FileTrait #287

• 3.x Update JsTrait #288

• 3.x Update KeyboardTrait #289

• 3.x Update LinkTrait #290

• 3.x Update MediaTrait #291

• 3.x Update MenuTrait #292

• 3.x Update MetaTagTrait #293

• 3.x Update ParagraphsTrait #294

• 3.x Update PathTrait #295

• 3.x Update ResponseTrait #296

• 3.x Update RoleTrait #297

• 3.x Update SelectTrait #298

• 3.x Update SearchApiTrait #299

• 3.x Update TaxonomyTrait #300

• 3.x Update UserTrait #301

• 3.x Update VisibilityTrait #302

• 3.x Update WaitTrait #303

• 3.x Add assertion that there are no JS errors on the page #272

• 3.x Add Drupal 11 build to the CI pipeline #319

[AlexSkrypnyk]

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

Add the following rules to the README.md:

• All types:

  • Avoid regexes in step definition comments. Use tuple format instead. It is easier to understand and maintain.
  • Use the following for tabled content.
  • Anything identified by a property should use with: Then the link :link with the title :title should exist
  • Use clear placeholder names to help the users to understand the expected value faster: content_type, not type
  • Do not use optional words like "(the|a)" and instead provide a single form. This helps with consistency.
  • Avoid on the page suffix - we are already on the page

• Given - states tests pre-requisites, something that should be created to be present before the test runs

  • Use exists, have
  • Do not use should or should not (these are used in assertions)
  • Avoid using I (these are for actions)

• When - defines an action, so should contain an action verb

  • Use I <verb>

• Then - asserts expectations

  • Use should and should not to clearly state that this is an assertion
  • Start with a "thing" you are asserting for: Then the link with a title :title exists
  • Do not use I