jhedstrom / drupalextension

An integration layer between Behat, Mink Extension, and Drupal.
GNU General Public License v2.0
209 stars 192 forks source link

Introduce a site building context #352

Open TravisCarden opened 7 years ago

TravisCarden commented 7 years ago

As mentioned in #343, I have a growing collection of custom step definitions I reuse frequently, and I'd like to contribute any of them that the community would benefit from. Following is a list of the steps I have currently. Would anyone like to see any of them in Drupal Extension? Do folks have their own steps that they reuse frequently (or would if they had them)? And, if it's decided that these don't belong in DrupalExtension, where should they go?

User roles & permissions:

Content types & fields:

pwolanin commented 7 years ago

@TravisCarden this certainly look useful. None of these look trivial for a novice to add and would be important for verifying site structure. I had been wanting exactly the check on the list of fields for a content type, for example.

jonathanjfshaw commented 7 years ago

If these were in this extension, they should probably be in a new "Sitebuilding" or "structure" context.

jhedstrom commented 6 years ago

I've also come across projects where folks really want to validate certain site configurations via Behat to ensure that they aren't accidentally changed. These could also go into a site building context...

TravisCarden commented 6 years ago

Note: Some of my step definitions have been released on Packagist as part of a specification tool we've created at Acquia: https://packagist.org/packages/acquia/drupal-spec-tool. See the announcement blog post on the Acquia Developer Center.