-
Notifications
You must be signed in to change notification settings - Fork 77
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
Add a test case to an existing test suite #644
Comments
I think approach 1 would work, where the task would say - if the directory exists and there's at least one file in it, then only generate the test module. |
@dmcassel I'm wondering about the value of this now - in practice, I just copy/paste an existing test, as that is likely to already be importing other libraries that are helpful for my tests. That seems easier than having to remember a Gradle task name and type out the correct arguments. |
@rjrudin fair enough. Is it worth having the |
The
mlGenerateUnitTestSuite
task will create a new test suite, but if you give it the name of an existing suite it will overwrite the setup and teardown modules. Allow generation of a new test case. This could be done a couple ways:mlGenerateUnitTestSuite
so that if the test suite already exists, it creates the new test case and skips all the setup/teardown.The text was updated successfully, but these errors were encountered: