Provide each Example with its own set of annotations

[brianjmiller]

I have a use case where I'd like to be able to dynamically mark a particular scenario as generated by an entry in an Examples table as pending. This patch provides a shallow clone of the original scenario annotations object for the individual table generated scenarios such that those scenarios can then be assigned a pending annotation (or any other really) and not have it effect the rest of the scenarios from that table. Normal marking of the scenario with @pending still causes all generated scenarios from the table to be pending.

I went with a shallow clone here because it was the easiest to implement. I'm not sure if ES5 code is acceptable. If ES3 would be preferred I can swap it out.

[brianjmiller]

Travis failed, but doesn't appear to be anything related to the code and make test passes over here. I have no way to re-kick it off since I'm not the primary project owner.

[cressie176]

Hi Brian,

I'll check it out thanks. You're right, the Travis build is nothing to do with you. There's a bug in node 0.10.31 which is causing a segmentation fault during the test run. The node guys are on top of it and have already created a fix.

Steve

[cressie176]

Published in 0.11.1

[brianjmiller]

Thanks! But I think you were right, should be key to key. I'm curious why my test worked though, I guess because pending just requires a truthy value and all of the resulting scenarios get that. It wouldn't work for annotations that take a value. I'll submit the correction.

[brianjmiller]

n/m, you got it and with tests. Excellent, thanks!