Legend:
- Unmodified
- Added
- Removed
-
trunk/README
r2 r4 33 33 1> make:all(). 34 34 35 then run the tests to ensure that xpdojois working on your platform:35 then run the tests to ensure that Extreme Forge is working on your platform: 36 36 37 37 2> xpdojo:test_files(".."). … … 43 43 44 44 This means that all unit and acceptance tests have passed. If the 45 numbers are different, some things are not working as expected. 45 two numbers following each phase (modules, unit, acceptance) are 46 different from each other, some things are not working as expected. 46 47 47 48 Using … … 53 54 54 55 Or, for a more interesting experience, run the continuous testing 55 server :56 server, e.g.: 56 57 57 4> testing_server:start("/some/path/to/source", fun(M) -> 58 io:fwrite("~p~n", [M]) end, xpdojo:default_options()). 58 4> Pids = testing_server:start("/some/path/to/source", "/tmp/log.txt"). 59 60 Then, "tail -f /tmp/log.txt" from shell or an emacs compilation buffer 61 to view the output. 62 63 To stop the testing_server: 64 65 5> testing_server:stop(Pids). 59 66 60 67 Read src/test_files_acceptance.erl for more details (such as -
trunk/ebin
-
Property
svn:ignore
set to
*.beam
-
Property
svn:ignore
set to
-
trunk/src/test_files_acceptance.erl
r2 r4 366 366 {Key, [{acceptance, 0, 0}, {unit, 1, 1}, {modules, 3, 3}]}}, 367 367 {fun() -> timer:sleep(1000),Silly_server_writer("domi") end, 368 %% No modification state so testing_server don't do anything !!! {Key, [{acceptance, 0, 0}, {unit, 1, 1}, {modules, 3, 3}]}}, 369 timeout}, 368 {Key, [{acceptance, 0, 0}, {unit, 1, 1}, {modules, 3, 3}]}}, 370 369 {fun() -> Silly ! {Self, key} end, 371 370 charpi},
Note: See TracChangeset
for help on using the changeset viewer.
