You can clone with
No one assigned
It would be a great addition if there was a behave tests runner. Maybe django-behave could be used to do the heavy lifting.
I've started working on a fix for this here: scottferg@38766c0
It still needs some work though. It doesn't appear to be reporting test results appropriately, which I believe is on django_behave's end. Need to look into it further to clean that up and get proper output to Jenkins.
Scratch that, looks like my local Behave was just out of date. It's a little bit of a mediocre experience since Behave considers the entire features/ directory to be a suite of tests, and there's no real way to separate each step into distinct Django tests. The output within Jenkins then becomes a dramatically reduced number of tests, and no real way to dig into the individual steps that failed short of viewing the console output. Not ideal, but it works for now. I'd like to dig into Behave itself and see if there's any possibility of allowing steps to be run individually, or at least per feature file.
@scottferg I think it looks good. Do I understand it correct that you get one test per application with features in the results?
Yes, some behave testing is better than no behave testing :). Do let me know when you're making a pull request.
Since #168 is open, I'm going to close this issue.