Mats Henricson <m...@henricson.se> wrote on 10/09/2009 14:59:32:
> How should we make Testify aware of asset and context?
> For example, we have this in our TML:
> ${context:/foo/bar/}
> Currently testify barfs at us like this:
>
> Caused by: java.lang.RuntimeException: Unable to locate asset
> 'context:foo/bar' (the file does not exist).
The TapestryTester has two constructors:
public TapestryTester(String appPackage, String appName, String
contextPath, Class<?>... moduleClasses)
public TapestryTester(String appPackage, Class<?>... moduleClasses)
In the first one you can define the path to the context; the second one
defaults to "src/main/webapp".
I believe this is with respect to the working directory that the test
process runs with.
So, if you have an error about the file not existing, I would check that
you are using the appropriate constructor (depending on whether the
default works for you) and whether you are running with the working
directory set to your project directory.
- Paul
---
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and delete this e-mail. Any unauthorized copying,
disclosure or distribution of the material in this e-mail is strictly forbidden.
Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional
EU corporate and regulatory disclosures.
