Given the interest shown at Drupalcon Portland with both a crowded session and BOF, the next step of fostering a growing use of Behat is to have a group of interested users/developers/etc. Behat, if embraced by enough Drupal folks, has the potential to vastly improve the way we test Drupal websites.
Behat IS NOT unit testing nor a specification testing tool. Behat is a Scenario-oriented BDD framework with functional testing capabilities as part of a communication process between stake-holders and developers. Behat was created and is evolving as an agile planning and functional testing methodology. However, if you want to use it as unit testing or spec testing tool, you can, but keep in mind, that it wasn't intended to do ideologically. http://groups.drupal.org/unit-testing is a better place for discussion of unit-testing. Yes, there is some overlap, but that is because of the spectrum in the testing pyramid with the various types of testing: unit tests (base), functional/acceptance tests (middle), (G)UI tests (peak)
Behat was created to address black-box like, functional, user-observable behavior testing.
Intro to Behat, setup, examples...
There is a lot of info out there for behat... might be nice to compile a list of Intros, setup tips/walkthroughs, and other examples (especially Drupal-y ones)
This discussion can be the start, and we'll turn it into a wiki shortly.
Read moreParallel runner for Behat
Hey guys!
Just want to let you know, that I've created a Behat extension, which allows parallel execution of tests. In most cases, using this extension should decrease test suite execution time a lot. For example, for my own project, it decreased execution time of full test suite from around 60 to 30 minutes (on my local machine).
Check it out and let me know what do you think.
Read more- « first
- ‹ previous
- 1
- 2
- 3

