forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject forrest test suites (Was: FOR-1072)
Date Sun, 02 Mar 2008 11:06:29 GMT
> Jeremias Maerki updated FOR-1072:
> ---------------------------------
> 
> BTW, where can I find this "forrest-sample-2" so I could run it myself? I've only run
"forrest seed" now.

Forrest has the following that can be used as tests. We don't have many
real testcases, just suites of documents that should exercise each piece
of functionality. Some automatically generated stuff is good test fodder.

'forrest seed' equates to 'forrest seed-sample' - our main test
(doing 'forrest -p' shows others).
Provides a local sample site to mess around with 'forrest run'
and 'forrest site'.

Create a new 'forrest seed' and follow the instructions
(in forrest.properties.dispatcher.properties) to enable the Dispatcher
work-in-progress. We call that "sample-2".

$FORREST_HOME/main/build.sh test
runs the 'site' target of both those samples.
... i should do this before committing, i should do this ...

The forrestbot on our zone runs them every two hours.
... so when we don't run 'build test', it catches us.
http://forrest.zones.apache.org/

cd $FORREST_HOME/site-author
forrest -f publish.xml build
would run the local forrestbot to build the forrest website.
(Deploy is a separate stage.)

Each plugin has its own documentation set. However, i think that
we don't have pdf output configured for their sites. It is easily
added locally if one needs specific plugin pdf tests.
We don't yet have a way to run all their 'site' targets at once.

So there are lots of chances to exercise FOP.

-David

Mime
View raw message