Skip to content

Commit 5bc36fb

Browse files
transclaude
andcommitted
Restore accidentally removed README sections
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent af070c9 commit 5bc36fb

1 file changed

Lines changed: 12 additions & 0 deletions

File tree

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,18 @@ The generator can take into account tests already written, so as not to include
103103

104104
$ lemons generate -Ilib lib/**/*.rb - test/**/*.rb
105105

106+
Test skeletons can be generated on a per-file or per-case bases. By case is the default. Use the `-f`/`--file` option to do otherwise.
107+
108+
$ lemon scaffold -f lib/foo.rb
109+
110+
The default output location is `test/`. You can change this with the `-o/--output` option.
111+
112+
Generating test case scaffolding from code will undoubtedly strike test-driven developers as a case of putting the cart before the horse. However, it is not unreasonable to argue that high-level, behavior-driven, functional testing frameworks, such as Q.E.D. and Cucumber, are better suited to test-first methodologies. While test-driven development can obviously be done with Lemon, unit-testing best suited to testing specific, critical portions of code, or for achieving full test coverage for mission critical applications.
113+
114+
### Test Directory
115+
116+
There is no special directory for Lemon tests. Since they are unit tests, `test/` or `test/unit/` are good choices. Other options are `cases/` and `test/cases` since each file generally defines a single test case.
117+
106118

107119
## COPYRIGHTS
108120

0 commit comments

Comments
 (0)