-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
What I personally find annoying when setting up a new project is creating the required test library and application.
At the moment for a library we need:
mylib-test-suite.dylanmylib-test-suite.lidmylib-test-suite-library.dylanmylib-test-suite-app.dylanmylib-test-suite-app.lidmylib-test-suite-app-library.dylan
And except file #1 they all contain some boilerplate stuff. The problem arises when we do like in dylan-foundry/sqlite-dylan and have two libraries with the test suites (sqlite and sqlite-database) but only one -app.
Maybe we could have two different commands, one to create the test suite library and one for the app, or have two different behaviors for the command whether the tests dir already contains an app or not.
Your thoughts?
Metadata
Metadata
Assignees
Labels
No labels