I have a Java project with a lot of classes. Now I want to get a list with all jUnit tests. My idea was to use grep for that.
So I navigated to the root folder, and use the following command:
grep junit -R ./ > output.txt
But obviously this isn't correct. So my question is. How is the correct command? And are there ways that are more easier to find jUnit tests?
find . -name *.java | egrep -R @Test . | cut -f1 -d" " | cut -f1 -d: > _1
If you've got junit 3 ones too, you could then run:
find . -name *Test.java >> _1
@Test annotations and pulling the filename out. Doesn't work on OSX, though, get repeated filenames w/ no contextual info. One reason I like ack :)You'd want:
grep -r junit *
But you need to be a little careful with that, as it'll go through all files, include jars.
Better to use find or ack:
ack --java -cl '@Test' # Print filenames with, and # occurences of, @Test annotations
Or more boringly:
find . -name *.java | xargs grep junit
ack --java junit # Or, more accurately:
ack --java 'import\s.*?junit.*'
find . -name "*.java" | xargs grep -il "junit"
In english:
Starting at the current directory, find all files that end in ".java".
For each file found, do a case-insensitive search for "junit".
If "junit" is found, print only the file name.
I would grep for "extends TestCase" - results likely are going to be more reliable
Any class that extends TestCase is automatically a JUnit class.
Depending on whether you use jUnit 3 or 4 you may not have @Test annotations
extend TestCase