Executable doesn't see units in other directories

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run a coverage test where the unit isn't in the current directory
2. if you specify the unit name only on the command line, an error is thrown 
(unit source not found)
3. if you specify the unit's relative path name, it is ignored, and the unit 
isn't marked for coverage.

What is the expected output? What do you see instead?

Expecting coverage information for the unit, but I see either nothing, or only 
the summary.

What version of the product are you using? On what operating system?

0.4

Please provide any additional information below.

Should provide ways to specify unit's paths other than the current paths, as it 
stands, it can only give coverage for the unit test units, but not for the 
units tested by the unit test (which are in various other directories, which 
are too numerous to put in the PATH environment variable).

Original issue reported on code.google.com by zar...@gmail.com on 30 Aug 2010 at 6:59

[GoogleCodeExporter]

To be more precise, only one directory can be given.

Original comment by zar...@gmail.com on 30 Aug 2010 at 7:10

[GoogleCodeExporter]

There is the parameters of -sp and -sd. Is this still an issue?

Original comment by ring....@gmail.com on 20 Oct 2011 at 12:41

[GoogleCodeExporter]

Original comment by ring....@gmail.com on 20 Oct 2011 at 12:41

• Changed state: Accepted

[GoogleCodeExporter]

-sp and -sd parameters are enough to specify one or more folders with units.
So this is fixed for me.

Original comment by trident.job on 20 Oct 2011 at 7:02

[GoogleCodeExporter]

You can close the issue.

Original comment by zar...@gmail.com on 21 Oct 2011 at 9:36

[GoogleCodeExporter]

Original comment by ring....@gmail.com on 21 Oct 2011 at 8:42

• Changed state: Verified