jeena/GGS
Archived
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

ggs_logger got lost somewhere? I added it again, also replaced all references to helpers with ggs_logger

Browse source
This commit is contained in:
Jonatan Pålsson 2011-02-17 08:33:55 +01:00
parent ea1557e2d7
commit 94d9dc6d7f
5 changed files with 23 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

8
tests/ggs_player_test.erl
View file

@ -4,20 +4,20 @@
%% @doc start_link should always return ok for any valid socket. A valid socket
%% should always return {ok, Pid} and {error, Reason} otherwise.
start_link_test() ->
helpers:not_implemented().
ggs_logger:not_implemented().
%% @doc Given that start_link returned {ok, Player}. Notify shall always return ok and
%% deliver a specified message through the socket.
notify_test() ->
helpers:not_implemented().
ggs_logger:not_implemented().
%% @doc Given that start_link returned {ok, Player}. get_token shall always return a valid
%% player token. a valid token should be unique.
get_token_test() ->
helpers:not_implemented().
ggs_logger:not_implemented().
%% @doc Given that start_link returned {ok, Pid}. There shouldn't be possible to
%% execute this function with the same Player and Table arguments twice.
stop_test() ->
helpers:not_implemented().
ggs_logger:not_implemented().