Open^H^H^H^HVisiting code & unit test files

Open^H^H^H^HVisiting code & unit test files

[Gary]

Is there any way to do the following without using some huge package
like cedet or something?

I have a project directory structure like this

myproject
 |
 |- Src
 |   |- Foo.php
 |   .
 |   ... more source files
 |
 |- Test
 |   |- Foo-Test.php
 |   .
 |   ... more unit test files
 etc.

In order for the unit test files (e.g. Foo-Test.php) to know what it
should test it includes some text like "require_once 'Foo.php';". The
include path is set when I actually run the unit test via the
Makefile. What I would like to happen is that when I put my cursor on
the "'Foo.php'" text, I can run find-file-at-point or something similar,
and have emacs visit myproject/Src/Foo.php without any further user
intervention. Currently I have to adapt the path manually.

If it helps, all unit test files are in the Test directory (or
subdirectories thereof) follow the naming convention x-Test.php, and
they correspond to the source file a matching named directory under Src
called x (where x is some descriptive name).

-- 
Gary
GNU Emacs 23.2.1
emacsclient 23.2
1.7.4(0.225/5/3) 2010-04-07 11:02 Cygwin

Re: Open^H^H^H^HVisiting code & unit test files

[Glauber Alex Dias Prado]

Gary <help-gnu-emacs@garydjones.name> writes:

> Is there any way to do the following without using some huge package
> like cedet or something?
>
> I have a project directory structure like this
>
> myproject
>  |
>  |- Src
>  |   |- Foo.php
>  |   .
>  |   ... more source files
>  |
>  |- Test
>  |   |- Foo-Test.php
>  |   .
>  |   ... more unit test files
>  etc.
>
> In order for the unit test files (e.g. Foo-Test.php) to know what it
> should test it includes some text like "require_once 'Foo.php';". The
> include path is set when I actually run the unit test via the
> Makefile. What I would like to happen is that when I put my cursor on
> the "'Foo.php'" text, I can run find-file-at-point or something similar,
> and have emacs visit myproject/Src/Foo.php without any further user
> intervention. Currently I have to adapt the path manually.
>
> If it helps, all unit test files are in the Test directory (or
> subdirectories thereof) follow the naming convention x-Test.php, and
> they correspond to the source file a matching named directory under Src
> called x (where x is some descriptive name).

Check out rinari it have a feature that makes this kind of association.