-
Notifications
You must be signed in to change notification settings - Fork 179
Parameterized suite, parameterized test + cmd commands #124
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
Conversation
Apparently it does not compile with older version than Visual Studio 2010, I will fix it soon |
Thanks for the PR. I'm a bit concerned about the size and scope of this. I realize that I don't have a contribution guide posted (bad maintainer, no Twinkie) -- but there are three (possibly more?) things going on here that are not all related:
At the least, they need to be broken up into separate PRs so the changes can be considered individually. That said, I don't want to waste your time on doing all that without offering some feedback first. Changing The new runner is something many people have done from outside of the framework, and I would not be opposed to adding an "official" one to the project. I don't think I grasp, though, why this one is as complicated as it is, or why the Finally, parameterized tests. I have a lot of issues with this feature as implemented, and frankly I feel that it's just... out of place. I think, if we worked together, we could come up with an implementation myself and the users would be happy with, but this is the kind of new feature that would really lend itself to a discussion ticket before being implemented. Of course, having a proposed implementation to start is helpful for the discussion. I don't want to discourage you from contributing, but I am closing this PR. Please feel free to continue the discussion here or on the issue board, and by all means open up separate PRs as you see fit. |
Hi John, Thank you for your review, I am a bit disappointed but not discouraged so I will improve until you can validate the PR ;) I will shortly tell you the story of the tests parameters : About the About the runner, I wrote it because of test parameters needs (for the parameter --ignoreparam, which is helpful). It is that much complicated because I tried to respect the way of the original I opened an issue, for discuss about the modifications that you would like. Best regards |
If you'd like to put the int->size_t changes into a pull request I'll take a look, although now that you point it out I may go after it if I don't see that PR in a few days. As for the runner, I'd be more interested in a simpler version that the user can just pass |
I will try to take time some time for make these two PRs this week |
Hi,
I spent some hours on my free time and at my work to develop two functionalities :
Actually I made cmd for the needs of the parameterized tests.
Important : Please note that I did not testes it on other platforms than Windows, in *.exe mode because I think you have more knowledges than me for this kind of testing :) Anyway the code is fully tested (see unittest-cpp\tests\TestParameterizedTest.cpp). Can I let you update the code for it works as a *.dll, *.lib, etc and for other platforms ?
For your test program you have to set the main this way :
And here is a basic example, the only macro you need is
SET_TEST_PARAMETER
:See file unittest-cpp\tests\TestParameterizedTest.cpp for more complex examples.
Best regards