Follow Us

Follow Us on Facebook Follow Us on Twitter

Quick Fix for CID Test Failure

Our *67 script failed when run in an interop scenario for the first time:

bash$ a_calls_b.py
a_calls_b
a_calls_bcd
a_calls_b_hangup
a_calls_b_ring_timeout
a_calls_b_anon_cid
ERROR: caller id string match error. Received 'anonymous', looking for 'Anonymous'. cid_mode=cid_anonymous
run_all_tests:17
 inner:45
  a_calls_b_anon_cid:118
   call:292
    place_call:353
     _check_cid:508
a_calls_b_terminator_hangup

Ok, that’s a pretty obvious failure — our expected CID string should have been all lowercase. No need to modify the script, just edit /etc/rimay/callgen.conf. Find this line:


[DEFAULT]
caller_id_anonymous_call_string = Anonymous

and change it to this:


[DEFAULT]
caller_id_anonymous_call_string = anonymous

Rerun the test:


bash$ a_calls_b.py a_calls_b_anon_cid
a_calls_b_anon_cid
bash$

Test passes!

This is in keeping with the overall strategy of keeping switch-specific details and behavior in the config file instead of in the scripts. As we can see here, it makes porting to a new interop scenario much easier.

Related posts:

  1. How to Get More Complete Test Coverage
  2. Creating Custom Test Suites on the Rimay Call Generator
  3. Why Do Experts Plan For Failure?

Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>