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
In multiple of my projects, I tend to change the structure of where my tests should go by default if no path has been specified. Since the majority of my tests go to tests/Feature, I want that to be the default path. However, there isn't currently a way to do this without messing with the script directly. Another use case would be to specify the base class. Since issue #135 is not backwards compatible, we could still make it happen without breaking anyone's tests by adding that as an option in the project level config file.
would we also automatically generate the paths for the phpunit.xml?
I personally don't find this a big deal, i just create the test and move it into the correct subgroup. That doesn't deal with the namespace though. So if you want this feature i say go for it but leave it optional?
In multiple of my projects, I tend to change the structure of where my tests should go by default if no path has been specified. Since the majority of my tests go to tests/Feature, I want that to be the default path. However, there isn't currently a way to do this without messing with the script directly. Another use case would be to specify the base class. Since issue #135 is not backwards compatible, we could still make it happen without breaking anyone's tests by adding that as an option in the project level config file.
The file would simply be a JSON file:
.testsuite.json
We could also easily allow for path options:
Then, for example, to create a chado importer test:
# Creates a test at tests/tripal_chado/importers/MyTest.php with the proper namespace tripaltest make:test --chado importers/MyTest
The resulting class would have the namespace:
If no path option is specified,
base_path
is used as the default or, if not provided, simply use the basetests
folder.Any thoughts? Other options to consider?
The text was updated successfully, but these errors were encountered: