At HQ we are working on acceptance testing both with headless browsers and regular browsers (using selenium webdriver) through behat and mink APIs, specifying the tests using a BDD syntax. The integration with Moodle is currently a "work in progress" the idea is to allow components and plugins to specify funcional tests like they do with phpunit.
More info in http://docs.moodle.org/dev/Acceptance_testing
Yes, we will go with Behat and Mink instead of the Java tests.
At the moment there are two issues and nothing is definitive. We are still deciding how to integrate Behat in Moodle (http://tracker.moodle.org/browse/MDL-35611) and on top of this issue there is the creation of basic steps and steps to group common tasks (http://tracker.moodle.org/browse/MDL-36269) which also needs more discussion and integrators approval.
I'd like to start using Behat-Moodle to do my development and tests. I know it's a work on progress... so can I use it right now?
By the way, I've using the repo:
So, what is the goal of the next projects? I mean, Are they necessary?:
Gracias y un saludo!
Thanks for asking because there were different projects, things changes fast, and it can be confusing. The main documentation page always up-to-date with the dev. status is http://docs.moodle.org/dev/Acceptance_testing
The behat-moodle project was part of the second option, but we found a better way to manage it and now is useless (in fact I've just deleted the project from my github account)
You can use it and all the feedback you can provide will be very appreciated but consider that it's not even integrated in master (future Moodle 2.5) so there can be changes. The main tracker issue is: http://tracker.moodle.org/browse/MDL-35611