Junit formatter for Behat 3.x

Posted by fen on January 6, 2015 at 9:16pm

Does anyone have the junit formatter working with behat 3.x?

I suppose there is a related question: is anyone using Behat 3.x with D7 site builds or is 2.x still the way to go?

Comments

Ah, just found the PR

Posted by fen on January 6, 2015 at 10:00pm

Looks like the PR is ready to go: https://github.com/Behat/Behat/pull/676

Can't wait ;)

Thanks for all the work!

How to configure the junit foormatter

Posted by fen on January 7, 2015 at 3:41am

I applied pull/676 to a fork of behat (yes, I know I'm jumping the gun) and I see the junit formatter is now available (via behat -h) - yay! But when I try to run e.g.

./vendor/bin/behat -f pretty,progress,junit --out ,${PROGRESS_LOG},logs/xml -c tests/behat/smoke.yml

I get:

[Behat\Testwork\Output\Exception\FormatterNotFoundException]                         
 pretty,progress,junit formatter is not found or has not been properly registered.

If I choose only junit, ("-f junit -o logs/xml") I get output in logs/xml/default.xml

I also tried this in my smoke.yml to no avail:

  formatters:
    pretty:
    progress: [logs/progress.log]
    junit: [logs/xml]

I am also waiting the release

Posted by mikaoelitiana@g... on February 9, 2015 at 2:58pm

I am also waiting the release for the support of junit format in 3.x. I am using this with D7 and I am using DrupalExtension 3. Do you recommend downgrading to 2.x for now?

Perhaps not the best solution...

Posted by fen on February 9, 2015 at 4:01pm

I applied the pull request to a local fork of Behat.

Now this works: behat -f junit --out logs/xml but it will be the only formatter. That is, I can get 'pretty' or 'junit' but not both ('pretty,junit'). But it supports jenkins, so I'm happy.

Note: I'm not sharing my fork as, once junit has been merged, I might do other experiments with the fork and I don't want to be responsible for breaking other's tests.