|
|
| Author |
Message |
|
| gordon guthrie |
 Posted: Sat Sep 02, 2006 3:23 pm |
 |
|
|
User
Joined: 02 Sep 2006
Posts: 17
|
I run test server a lot.
Test suite are written around types of test and then standard versions of:
* init_per_testcase
* end_per_testcase
* init_per_suite
* end_per_suite
are used to set up and tear down the environment
My test cases are kept under version control in parallel with the source and the init/end routes call stubs that start the application which can be a local Erlang node if you are doing Unit testing, but may start a remote node if, for instance, you are testing a web-site written in Erlang and want to fire in posts and see what the site does.
I have also written a bash script which enables the test server to be run as part of a production Erlang suite. This is available from the jungerl and is called erlang_automated_build
It is documented at:
http://jungerl.cvs.sourceforge.net/jungerl/jungerl/lib/erlang_automated_build/doc/DOCUMENTATION.TXT?view=markup
Using erlang_automated_build you can cron job a build script which does:
* a CVS checkout
* compiles your source code
* runs a set of tests
* runs the dialyzer
It will report on sucess or failure and graph the results continuously using gnuplot.
I have an ugly and unreleasable spider for web link testing that I will include at some stage when/if it is fit for human consumption...
Gordon |
|
|
| Back to top |
 
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
