8000 GitHub - swarmcom/busytone: Reach test suite
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

swarmcom/busytone

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

BusyTone

Reach functional tests and framework. This is work in progress, see TODO. The ultimate goal is to convert all manual tests to automatic ones, probably linking them together.

Notes

Relies heavily on mod_erlang_event, also requires FreeSWITCH drone to operate.

call_sup:originate/1 and call_sup:originate/2 anchor calls back to BusyTone to manage, the same way as incoming calls gets in, therefore no additional tricks required to get channel events/updates.

call:match_for/2 matches online calls for Channel Variable set. call:variables/1 collects variables.

You can alter test suite verbosiness with test_sup:debug(), test_sup:info() and test_sup:notice() commands.

Test cases

Test cases should be put to src/tests folder, and named like t_${Test Name}.erl (suite runner will match module names with this pattern). If test case file is altered it gets dynamically compiled and reloaded.

Example session

(busytone@172.17.0.1)149> test_sup:notice().
ok
(busytone@172.17.0.1)150> test_sup:run().
2017-07-07 11:04:10.747 <0.2466.0> notice test_sup.63 test:t_seq_login result:ok
2017-07-07 11:04:10.956 <0.2466.0> notice test_sup.63 test:t_simple_inqueue result:ok
2017-07-07 11:04:12.988 <0.2466.0> notice test_sup.63 test:t_seq_pickup result:ok
2017-07-07 11:04:13.916 <0.2466.0> notice test_sup.63 test:t_simple result:ok
ok
(busytone@172.17.0.1)151> test_sup:run(t_seq_login).
2017-07-07 11:05:09.099 <0.2466.0> notice test_sup.63 test:t_seq_login result:ok
ok

About

Reach test suite

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

0