ahawker/cookie-sheet

Create repositories from Cookiecutter templates

cookie-sheet's Issues

Refactor to support individual features

TODO

Target for compilation?

We should support a target for a build/compilation step for non-interpreted languages.

Pattern matching test targets

As of today, there are three test related targets:

• make test-integration
• make test-interface
• make test-unit

These can be invoked individually or as prerequisites of make test.

However, naming tests is a nightmare. No one follows any of the same standards. Integration tests are what? Integrations within this code base? Within a smaller set of services? Integrating within the entire system? Yada, yada, yada...

What the interface should expose statically is:

• make test

What the interface should expose dynamically is:

• make test-%

Where % is pattern matching against all files within scripts/ that match this test-* pattern. The downside of this is that I believe the make (usage|help) output will not contain entries for these dynamically created targets. Is that a big enough issue to warrant hand defining each target?