source: tags/2007Q2/README @ 4

Revision 4, 3.4 KB checked in by dom, 5 years ago (diff)

Updated README and acceptance tests for improved testing_server

Line 
1EXTREME FORGE
2
3http://www.extremeforge.net
4
5The aims of this software are:
6
7* To provide a complete, self-contained environment fulfilling the
8  needs of extreme programming teams.
9* To explore some of the ideas at the forefront of extreme
10  programming.
11* To facilitate adoption of extreme programming in corporate
12  environments, by automating or simplifying traditional needs such
13  as traceability, tracking, reporting, metrics...
14* To facilitate the use of extreme programming on distributed
15  projects, including open source ones.
16
17Requirements
18-----------
19
20Erlang/OTP R10B4 or above.
21
22Installation
23------------
24
25Download the tarball, unpack to any convenient location.
26Change to the ./ebin subdirectory, then
27start an erlang shell in distributed mode, e.g.:
28
29% erl -sname forge
30
31Then, from the erlang shell prompt, first compile:
32
331> make:all().
34
35then run the tests to ensure that Extreme Forge is working on your platform:
36
372> xpdojo:test_files("..").
38
39After some output (including process crashes, they are part of the
40testing process), you should get a last line of output like this:
41
42[{acceptance,39,39},{unit,101,101},{modules,27,27}]
43
44This means that all unit and acceptance tests have passed. If the
45two numbers following each phase (modules, unit, acceptance) are
46different from each other, some things are not working as expected.
47
48Using
49-----
50
51You can now test any source tree of your own in the same way:
52
533> xpdojo:test_files("/some/path/to/source").
54
55Or, for a more interesting experience, run the continuous testing
56server, e.g.:
57
584> Pids = testing_server:start("/some/path/to/source", "/tmp/log.txt").
59
60Then, "tail -f /tmp/log.txt" from shell or an emacs compilation buffer
61to view the output.
62
63To stop the testing_server:
64
655> testing_server:stop(Pids).
66
67Read src/test_files_acceptance.erl for more details (such as
68defining your own rules for detecting unit and acceptance tests).
69
70LEGAL MATTERS
71-------------
72
73The software contained herein is:
74
75Copyright (c) 2004-2007 Dominic Williams, Nicolas Charpentier,
76Fabrice Nourisson, Jacques Couvreur, Virgile Delecolle.
77All rights reserved.
78
79Redistribution and use in source and binary forms, with or without
80modification, are permitted provided that the following conditions are
81met:
82
83* Redistributions of source code must retain the above copyright
84  notice, this list of conditions and the following disclaimer.
85* Redistributions in binary form must reproduce the above copyright
86  notice, this list of conditions and the following disclaimer in the
87  documentation and/or other materials provided with the distribution.
88* The names of the authors may not be used to endorse or promote
89  products derived from this software without specific prior written
90  permission.
91
92THIS SOFTWARE IS PROVIDED BY THE AUTHORS "AS IS" AND ANY EXPRESS OR
93IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
94WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
95DISCLAIMED. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY DIRECT,
96INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
97(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
98SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
99HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
100STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
101IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
102POSSIBILITY OF SUCH DAMAGE.
Note: See TracBrowser for help on using the repository browser.