No test coverage for the frontend.
This wouldn't be a replacement for SimpleTest, but likely all the SimpleTests using the browser could be moved over.
There will be things we can't do with Behat, but we can tackle those separately.
Quote from catch's comment at.
I'd like to keep this issue clean and at a reasonable amount of comments. Let's file follow-ups for specific topics that needs to be agreed on, that worked very well for the JS meta clean-up.
Realistically we can't get started until we get at least a couple examples of implementation. I'll be talking with a few people this week already, I know jessebeach is as well. If you have a project using behat, please reach out to your closest JS maintainer to talk about it.
- Get feedback from projects using behat in the wild and sum that up somewhere.
- Reach out to Behat developers to see if/when they can help us out.
- Agree on how to implement this for core and contrib (where are test files, standards for writing tests, etc.).
- Make d.o testbot run behat tests
User interface changes
Probably none, only additions.
People and groups involved
|FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 74,821 pass(es), 16 fail(s), and 0 exception(s).|
|FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 72,672 pass(es), 16 fail(s), and 0 exception(s).|
|FAILED: [[SimpleTest]]: [PHP 5.4 MySQL] 72,188 pass(es), 61 fail(s), and 0 exception(s).|