Description:
A graphical interface to creating Behat/Gherkin tests and running them.

You can see a video here https://www.youtube.com/watch?v=rX3_2yift2k
I allows a user to write behat tests and run them saving results to the database so they can see a history of the test. It allows for tagging of tests, bulk running of tests by tags or folders.

It builds off of DrupalExtension module https://drupal.org/project/drupalextension to allow other developers to add to its Behat Step Definitions.

Also it has another module (I will post shortly) to allow it to communicate to Saucelabs so your tests can run there while you watch. (that module is here https://github.com/alnutile/behat_editor_saucelabs)

And a cron runner module to run critical tests for wormly like reports (will post after this) https://github.com/alnutile/behat_editor_cronrunner

The Sandbox is here
https://drupal.org/sandbox/yurtboy/2147707

Thanks!

Comments

PA robot’s picture

PA robot commented
Status: Active » Needs work

There are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandboxyurtboy2147707git

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

b2f’s picture

b2f commented

I am very interested in your module, as I am working on a multiple purpose solution for BDD in Drupal - facilitating the use of drupal extension.

First of all, you should really consider trying to apply a smaller project - reviewers do it on their free time and your module is quite big to discourage most of us. Plus it will probably take forever to find and fix most issues as it is already long with smaller project.

Coding standards and style

The automated review above found some errors you should fix to get reviewed quicker, but I'm impressed you mostly got it right ! Well done :)

However, you are working on the master branch, please delete it and add the 7.x-1.x branch instead.

Installation

When enabling with drush, libraries download links are not showing properly because my terminal can't display them - you may display the link path in its title for drush users.

That being said, I installed the libraries and moved them to data_table, date_format and tag_it directories to match your .install hook_requierements, but I failed to make it work. Can you provide me with detailed installation steps for libraries dependencies ?

Module's organisation

I am not sure why you expose a composer.json and readme.md files. Maybe you should consider splitting your project so that it interfaces with composer manager to get composer related files in a dedicated directory.

Good luck on your project application.

yurtboy’s picture

yurtboy commented

Thanks for all the feedback! And sorry for the delay, my new Sanebox setup made it easy to miss it in my email box. I will follow up on the results and comments asap. Maybe by the end of this week.

PA robot’s picture

PA robot commented
Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application (see also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.