Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NUnit TestCase support #1

Open
DamianReeves opened this issue Sep 12, 2013 · 3 comments
Open

NUnit TestCase support #1

DamianReeves opened this issue Sep 12, 2013 · 3 comments

Comments

@DamianReeves
Copy link

DamianReeves commented Sep 12, 2013

The outputted text doesn't seem to properly support the [TestCase] attribute in NUnit.

@copypastedeveloper
Copy link
Owner

I've been trying to think of how to properly support this scenario for a while. I'd love to add test case support. The main thing has always been how to handle the execution of the context. i've also always been torn because in theory a bdd test probably encapsulates a scenario. i think changing the variables would fundamentally change the test case. it could be that you just implement a base, or you could potentially look into using the ContextProvider class, as it would allow you to reuse contexts across multiple test cases.

How would you ideally like to see this implemented?

@DamianReeves
Copy link
Author

Somehow Example support would need to be added.

Off the top of my head.

Examples<string> with_examples = ()=>{
   return new []{
       "first.last@email.com",
       "namel@email.com",    
   }
};

@copypastedeveloper
Copy link
Owner

yeah, that'd be pretty difficult to implement, and i'm not sure of the value of it. my main thought with a bdd style test is, again, that the test should look like exactly one scenario. test cases like nunit has almost explicitly are running multiple scenarios through the same code. if i was to implement this it might be through some kind of class level attributing, where the entire class is augmented/changed in some way per attribute, but then, because i'm wrapping multiple frameworks you get into the problem with a general lack of feature parity. at any rate, this is probably a ways off. i'll chew on it a little more though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants