Fleshing out Generation System Tests

[clrudolphi]

First commit to flesh out the Generation System Test suite. Per TODO comments in the code, added test methods to confirm system test integration of Failing, Pending, Ignored, and Undefined scenarios/tests.

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue).
• [ ] New feature (non-breaking change which adds functionality).
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
• [ ] Performance improvement
• [ ] Refactoring (so no functional change)
• [X ] Other (docs, build config, etc)

Checklist:

• [X] I've added tests for my code. (most of the time mandatory)
• [ ] I have added an entry to the changelog. (mandatory)
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.

[clrudolphi]

@gasparnagy Could use your help pointing me in the right direction. Seeing inconsistent results across testing Frameworks.

• MSTest treats undefined tests as Ignored, but the other frameworks treat them as Pending.
• For Ignored tests: NUnit counts the number of physical tests (scenarios plus scenario outline example rows), while the other two frameworks count only the number of Scenarios.

Also, would appreciate feedback on the general direction I'm taking here. Is this consistent with your vision for these tests?

[gasparnagy]

@clrudolphi I see. This is a bit more complicated then. I would need to play with that next week to figure out how to move on, so let's suspend this until next week.

[clrudolphi]

I looked at what Specs did for the same types of tests and adjusted accordingly.

[gasparnagy]

@clrudolphi Thx! Sorry for not being very supportive last week... Spring vs Reqnroll: 1-0 :)

I will take over this and play with it a bit more in the upcoming days.

[gasparnagy]

moved overt to the main repo branch as #99