You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Modify mlGenerateUnitTestSuite so that if the test suite already exists, it creates the new test case and skips all the setup/teardown.
Create a new task for generating only test cases.
The text was updated successfully, but these errors were encountered:
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 mlGenerateUnitTestSuite task see that the target directory already exists and decline to go further, to avoid overwriting things? Or good enough to rely on git's ability to restore?
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: