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

ISUP Manager Testplan

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

Code Reviewed By:

Unit Tested By:

ISUP - ISUP: Successful call; release from next exchange - isup_mgr1

Legs Taken:

  • Outgoing call through
  • Call release received from called side

Testplan:

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

CR:

UT:
2. Mail iam to isup_mgr1 (Message from env_l)
  1. iam message handler should be called
  2. isup_mgr1 should allocate resource "Incoming Trunk"
  3. isup_mgr1 should create task isup_call1
  4. isup_mgr1 should send iam to isup_call1

CR:

UT:
3. Mail call_over to isup_mgr1 (Message from isup_call1)
  1. call_over message handler should be called
  2. isup_mgr1 should delete task isup_call1
  3. isup_mgr1 should free resource "Incoming Trunk"

CR:

UT:

ISUP - ISUP: Successful call; release from next exchange - isup_mgr2

Legs Taken:

  • Outgoing call through
  • Call release received from called side

Testplan:

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

CR:

UT:
2. Mail call_request to isup_mgr2 (Message from isup_call1)
  1. call_request message handler should be called
  2. isup_mgr2 should allocate resource "Outgoing Trunk"
  3. isup_mgr2 should create task isup_call2
  4. isup_mgr2 should send call_request to isup_call2

CR:

UT:
3. Mail call_over to isup_mgr2 (Message from isup_call2)
  1. call_over message handler should be called
  2. isup_mgr2 should delete task isup_call2
  3. isup_mgr2 should free resource "Outgoing Trunk"

CR:

UT:

ISUP - ISUP: Successful call; release from previous exchange - isup_mgr1

Legs Taken:

  • Outgoing call through
  • Call release received from calling side

Testplan:

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

CR:

UT:
2. Mail iam to isup_mgr1 (Message from env_l)
  1. iam message handler should be called
  2. isup_mgr1 should allocate resource "Incoming Trunk"
  3. isup_mgr1 should create task isup_call1
  4. isup_mgr1 should send iam to isup_call1

CR:

UT:
3. Mail call_over to isup_mgr1 (Message from isup_call1)
  1. call_over message handler should be called
  2. isup_mgr1 should delete task isup_call1
  3. isup_mgr1 should free resource "Incoming Trunk"

CR:

UT:

ISUP - ISUP: Successful call; release from previous exchange - isup_mgr2

Legs Taken:

  • Outgoing call through
  • Call release received from calling side

Testplan:

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

CR:

UT:
2. Mail call_request to isup_mgr2 (Message from isup_call1)
  1. call_request message handler should be called
  2. isup_mgr2 should allocate resource "Outgoing Trunk"
  3. isup_mgr2 should create task isup_call2
  4. isup_mgr2 should send call_request to isup_call2

CR:

UT:
3. Mail call_over to isup_mgr2 (Message from isup_call2)
  1. call_over message handler should be called
  2. isup_mgr2 should delete task isup_call2
  3. isup_mgr2 should free resource "Outgoing Trunk"

CR:

UT:

ISUP - ISUP: Outgoing call failed - isup_mgr1

Leg Taken:

  • Outgoing call failed

Testplan:

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

CR:

UT:
2. Mail iam to isup_mgr1 (Message from env_l)
  1. iam message handler should be called
  2. isup_mgr1 should allocate resource "Incoming Trunk"
  3. isup_mgr1 should create task isup_call1
  4. isup_mgr1 should send iam to isup_call1

CR:

UT:
3. Mail call_over to isup_mgr1 (Message from isup_call1)
  1. call_over message handler should be called
  2. isup_mgr1 should delete task isup_call1
  3. isup_mgr1 should free resource "Incoming Trunk"

CR:

UT:

ISUP - ISUP: Outgoing call failed - isup_mgr2

Leg Taken:

  • Outgoing call failed

Testplan:

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

CR:

UT:
2. Mail call_request to isup_mgr2 (Message from isup_call1)
  1. call_request message handler should be called
  2. isup_mgr2 should allocate resource "Outgoing Trunk"
  3. isup_mgr2 should create task isup_call2
  4. isup_mgr2 should send call_request to isup_call2

CR:

UT:
3. Mail call_over to isup_mgr2 (Message from isup_call2)
  1. call_over message handler should be called
  2. isup_mgr2 should delete task isup_call2
  3. isup_mgr2 should free resource "Outgoing Trunk"

CR:

UT:

ISUP - V5.2: Successful call - isup_mgr1

Legs Taken:

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

Testplan:

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

CR:

UT:
2. Mail iam to isup_mgr1 (Message from env_l)
  1. iam message handler should be called
  2. isup_mgr1 should allocate resource "Incoming Trunk"
  3. isup_mgr1 should create task isup_call1
  4. isup_mgr1 should send iam to isup_call1

CR:

UT:
3. Mail call_over to isup_mgr1 (Message from isup_call1)
  1. call_over message handler should be called
  2. isup_mgr1 should delete task isup_call1
  3. isup_mgr1 should free resource "Incoming Trunk"

CR:

UT:

ISUP - V5.2: CSH timeout - isup_mgr1

Legs Taken:

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

Testplan:

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

CR:

UT:
2. Mail iam to isup_mgr1 (Message from env_l)
  1. iam message handler should be called
  2. isup_mgr1 should allocate resource "Incoming Trunk"
  3. isup_mgr1 should create task isup_call1
  4. isup_mgr1 should send iam to isup_call1

CR:

UT:
3. Mail call_over to isup_mgr1 (Message from isup_call1)
  1. call_over message handler should be called
  2. isup_mgr1 should delete task isup_call1
  3. isup_mgr1 should free resource "Incoming Trunk"

CR:

UT:

ISUP - V5.2: Outgoing call failed - isup_mgr1

Leg Taken:

  • Called Subscriber is busy

Testplan:

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

CR:

UT:
2. Mail iam to isup_mgr1 (Message from env_l)
  1. iam message handler should be called
  2. isup_mgr1 should allocate resource "Incoming Trunk"
  3. isup_mgr1 should create task isup_call1
  4. isup_mgr1 should send iam to isup_call1

CR:

UT:
3. Mail call_over to isup_mgr1 (Message from isup_call1)
  1. call_over message handler should be called
  2. isup_mgr1 should delete task isup_call1
  3. isup_mgr1 should free resource "Incoming Trunk"

CR:

UT:

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

Legs Taken:

  • Called Subscriber is free
  • Called Subscriber does not answer

Testplan:

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

CR:

UT:
2. Mail iam to isup_mgr1 (Message from env_l)
  1. iam message handler should be called
  2. isup_mgr1 should allocate resource "Incoming Trunk"
  3. isup_mgr1 should create task isup_call1
  4. isup_mgr1 should send iam to isup_call1

CR:

UT:
3. Mail call_over to isup_mgr1 (Message from isup_call1)
  1. call_over message handler should be called
  2. isup_mgr1 should delete task isup_call1
  3. isup_mgr1 should free resource "Incoming Trunk"

CR:

UT:

V5.2 - ISUP: Successful call - isup_mgr2

Leg Taken:

  • Outgoing call through

Testplan:

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

CR:

UT:
2. Mail call_request to isup_mgr2 (Message from v5_call1)
  1. call_request message handler should be called
  2. isup_mgr2 should allocate resource "Outgoing Trunk"
  3. isup_mgr2 should create task isup_call2
  4. isup_mgr2 should send call_request to isup_call2

CR:

UT:
3. Mail call_over to isup_mgr2 (Message from isup_call2)
  1. call_over message handler should be called
  2. isup_mgr2 should delete task isup_call2
  3. isup_mgr2 should free resource "Outgoing Trunk"

CR:

UT:

V5.2 - ISUP: Outgoing call failed - isup_mgr2

Leg Taken:

  • Outgoing call failed

Testplan:

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

CR:

UT:
2. Mail call_request to isup_mgr2 (Message from v5_call1)
  1. call_request message handler should be called
  2. isup_mgr2 should allocate resource "Outgoing Trunk"
  3. isup_mgr2 should create task isup_call2
  4. isup_mgr2 should send call_request to isup_call2

CR:

UT:
3. Mail call_over to isup_mgr2 (Message from isup_call2)
  1. call_over message handler should be called
  2. isup_mgr2 should delete task isup_call2
  3. isup_mgr2 should free resource "Outgoing Trunk"

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.