EventHelix.com: CASE Tools; Real-time and Embedded System Design; Object Oriented Design
  Home  |  EventStudio System Designer 4.0  |  VisualEther Protocol Analyzer 1.0  |  Real-time Mantra  |  Contact Us

V5.2 Manager Testplan

Generated by EventStudio 1.0.2 on 22-Oct-00 19:27

Code Reviewed By:

Unit Tested By:

V5.2 - V5.2: Successful call - v5_mgr1

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is free
  • Called Subscriber answers
  • Calling Subscriber hangs up

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:

V5.2 - V5.2: Successful call - v5_mgr2

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is free
  • Called Subscriber answers
  • Calling Subscriber hangs up

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from v5_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should allocate resource "Called Port"
  3. v5_mgr2 should create task v5_call2
  4. v5_mgr2 should send call_request to v5_call2

CR:

UT:
3. Mail call_over to v5_mgr2 (Message from v5_call2)
  1. call_over message handler should be called
  2. v5_mgr2 should delete task v5_call2
  3. v5_mgr2 should free resource "Called Port"

CR:

UT:

V5.2 - V5.2: CSH timeout - v5_mgr1

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is free
  • Called Subscriber answers
  • Called Subscriber goes onhook

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:

V5.2 - V5.2: CSH timeout - v5_mgr2

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is free
  • Called Subscriber answers
  • Called Subscriber goes onhook

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from v5_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should allocate resource "Called Port"
  3. v5_mgr2 should create task v5_call2
  4. v5_mgr2 should send call_request to v5_call2

CR:

UT:
3. Mail call_over to v5_mgr2 (Message from v5_call2)
  1. call_over message handler should be called
  2. v5_mgr2 should delete task v5_call2
  3. v5_mgr2 should free resource "Called Port"

CR:

UT:

V5.2: E1 slot not available - v5_mgr1

Leg Taken:

  • E1 slot not available for V5.2 Subscriber

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:

V5.2: Partial dialling - v5_mgr1

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • No Dialling or Partial Dialling

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail ll0 to v5_mgr1 (Message from v5_call1)
  1. ll0 message handler should be called

CR:

UT:
4. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"
  4. v5_mgr1 should take action "Mark Calling Port in LLO"

CR:

UT:

V5.2: Directory number unknown - v5_mgr1

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Call failed: DN unknown or All trunks to the Route are busy

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:

V5.2: Called subscriber is busy - v5_mgr1

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is busy
  • Calling Subscriber goes onhook on hearing Busy tone

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:

V5.2: Called subscriber is busy - v5_mgr2

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is busy
  • Calling Subscriber goes onhook on hearing Busy tone

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from v5_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should send call_request_nack to v5_call1

CR:

UT:

V5.2: Called subscriber does not answer - v5_mgr1

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is free
  • Called Subscriber does not answer
  • Calling Subscriber clears on hearing Congestion

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:

V5.2: Called subscriber does not answer - v5_mgr2

Legs Taken:

  • E1 slot available for V5.2 Subscriber
  • DTMF Dialling Subscriber
  • Complete Dialling
  • Routing is successful
  • Called Subscriber is free
  • Called Subscriber does not answer
  • Calling Subscriber clears on hearing Congestion

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from v5_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should allocate resource "Called Port"
  3. v5_mgr2 should create task v5_call2
  4. v5_mgr2 should send call_request to v5_call2

CR:

UT:
3. Mail call_over to v5_mgr2 (Message from v5_call2)
  1. call_over message handler should be called
  2. v5_mgr2 should delete task v5_call2
  3. v5_mgr2 should free resource "Called Port"

CR:

UT:

ISUP - V5.2: Successful call - v5_mgr2

Legs Taken:

  • Called Subscriber is free
  • Called Subscriber answers
  • Call release received from previous exchange

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from isup_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should allocate resource "Called Port"
  3. v5_mgr2 should create task v5_call2
  4. v5_mgr2 should send call_request to v5_call2

CR:

UT:
3. Mail call_over to v5_mgr2 (Message from v5_call2)
  1. call_over message handler should be called
  2. v5_mgr2 should delete task v5_call2
  3. v5_mgr2 should free resource "Called Port"

CR:

UT:

ISUP - V5.2: CSH timeout - v5_mgr2

Legs Taken:

  • Called Subscriber is free
  • Called Subscriber answers
  • Called Subscriber goes onhook

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from isup_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should allocate resource "Called Port"
  3. v5_mgr2 should create task v5_call2
  4. v5_mgr2 should send call_request to v5_call2

CR:

UT:
3. Mail call_over to v5_mgr2 (Message from v5_call2)
  1. call_over message handler should be called
  2. v5_mgr2 should delete task v5_call2
  3. v5_mgr2 should free resource "Called Port"

CR:

UT:

ISUP - V5.2: Outgoing call failed - v5_mgr2

Leg Taken:

  • Called Subscriber is busy

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from isup_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should send call_request_nack to isup_call1

CR:

UT:

ISUP - V5.2: Called subscriber does not answer - v5_mgr2

Legs Taken:

  • Called Subscriber is free
  • Called Subscriber does not answer

Testplan:

Num Action Result Status
1. Create task v5_mgr2
  1. Check if task v5_mgr2 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail call_request to v5_mgr2 (Message from isup_call1)
  1. call_request message handler should be called
  2. v5_mgr2 should allocate resource "Called Port"
  3. v5_mgr2 should create task v5_call2
  4. v5_mgr2 should send call_request to v5_call2

CR:

UT:
3. Mail call_over to v5_mgr2 (Message from v5_call2)
  1. call_over message handler should be called
  2. v5_mgr2 should delete task v5_call2
  3. v5_mgr2 should free resource "Called Port"

CR:

UT:

V5.2 - ISUP: Successful call - v5_mgr1

Leg Taken:

  • Outgoing call through

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:

V5.2 - ISUP: Outgoing call failed - v5_mgr1

Leg Taken:

  • Outgoing call failed

Testplan:

Num Action Result Status
1. Create task v5_mgr1
  1. Check if task v5_mgr1 data-structures and objects have been initialized correctly

CR:

UT:
2. Mail establish to v5_mgr1 (Message from env_l) with parameters offhook
  1. establish message handler should be called
  2. v5_mgr1 should allocate resource "Calling Port"
  3. v5_mgr1 should create task v5_call1
  4. v5_mgr1 should send establish to v5_call1 with fields offhook

CR:

UT:
3. Mail call_over to v5_mgr1 (Message from v5_call1)
  1. call_over message handler should be called
  2. v5_mgr1 should delete task v5_call1
  3. v5_mgr1 should free resource "Calling Port"

CR:

UT:
 
  Home  |  EventStudio System Designer 4.0  |  VisualEther Protocol Analyzer 1.0  |  Real-time Mantra  |  Contact Us
Copyright © 2000-2008 EventHelix.com Inc. All Rights Reserved.