Open snowe2010 opened 9 years ago
At a glance this looks like a character issue, most likely in a feature/scenario name or step definition matcher. If you can, hunt down the offending file and identify any unicode character that might have been introduced. If this is a recent issue I'd start with the latest code submitted. I'll try and follow up on this in the next week.
Another option is to open the formatter class in the gem and print out the output before the failure and post it here and I can pick through it, if you don't feel comfortable doing that I more than understand.
Yeah that's the thing, it only happens when I run it inline. I can run through the command line with output as html and it works perfectly fine.
I did find some unicode characters, took a while though. It was opening and closing double quotes instead of straight quotes. I don't understand why it worked running through the command line though, writing to the same output.
It does work now btw.
Marking this as a bug so that we can revisit it. If you could provide us the offending source file that caused the issue that would be lovely. Otherwise replication may not be possible at time of analysis.
I'm getting an InvalidByteSequenceError when attempting to use cuke_sniffer inline. I've got these lines in my env.rb file
When I run cucumber I get this error when it tries to write the file.