Chinaunix首页 | 论坛 | 博客
  • 博客访问: 19881681
  • 博文数量: 679
  • 博客积分: 10495
  • 博客等级: 上将
  • 技术积分: 9308
  • 用 户 组: 普通用户
  • 注册时间: 2006-07-18 10:51
文章分类

全部博文(679)

文章存档

2012年(5)

2011年(38)

2010年(86)

2009年(145)

2008年(170)

2007年(165)

2006年(89)

分类: 项目管理

2007-03-14 09:57:05

一,目的明确,有具体的输入输出

Purpose

以前的目的 

Verify if the CDR is right about user order tvod program

修改后

Verify that while TVOD ordered from EPG CDR record created correctly


Input data and out put data shall be described clearly

 二,有明确的步骤和检查点

Step

1.MC sigon

2.Enter 'TVOD' at EPG

3.Select one TVOD program

4.Order the tvod program

5.Check the cdr that build by AC

/opt/utoss/accountcenter/chargedata/online/succ


 

1.Enter 'TVOD' at EPG

2.Select a TVOD program

3.Order the tvod program

4.Open cdr (file) which exists on AC under

/opt/utoss/accountcenter/chargedata/online/succ

5.Check the value pending after tag "7/" matches the service ID

 

Clear steps and check point

 


三,准备要求是数据的准备

Precondition

1.OSS is normal

2.Billing of TVOD had config at OSS

3.Have one MC

4.VSLR/PSC/EPG/USC/AC is normal

 

1 Find or create IPTV subscriber refer to TC IDxxxx1, give UserID

2.Find a TVOD from OSS refer to TC IDxxxx2

3.Get "ServiceID" from "Service" table on OSS db by giving UserID

4.Install new subscriber on MC refer to TC IDxxxx3 or sign on  MC refer to TC IDxxxx4

 

Not environment preparation, it should be detail data preparation to meet this test case needs. (it’s better to refer to test case ID, if it’s too difficult, at least give the test case set path.)

 

1.User can order the tvod program

2.AC can write the cdr after user order the tvod program

/opt/utoss/server/accountcenter/chargedata/online/succ/

3.Every tag of the cdr is right

 

1. AccountCenter can write the cdr after user order the TVOD program, there should be a record about the user order the TVOD

2. Check specified field 7 of the cdr, it should eauql to the serviceid of the user

Clearly describe the expected result which matched the output data descript in “Test Purpose”

 

 

case 2:

 

Purpose

NMS support browse chassis inventory inside CO

Verify that chassis inventory shall be browsed on NMS CO Physical View, and chassis id from inventory is matched with chassis id from blade of the chassis

 

 

1. Login NMS

2. Open one physical view

3. Browse chassis inventory inside CO

4. Check the result and compare these data with real information

 

Step

1. Login NMS

2. Open one real CO's s physical view.

3. Browse chassis inventory on CO physical view, select any one chassis, get its ChassisID (SRS or HLD must provide enough information such as “look and view” or operation flow, comments by Norten)

4. Browse blade inventory on CO physical view, select any one blade of selected chassis, get its BladeIP

5. Telnet on the selected blade, get chassis id from /usr/local/rss/chassis_id file

6. Compare the chassis id from inventory with chassis id from blade

 

Precondition

Master Chassis Manager run normally

NMS run normally

Some NE run normally

 

At least one real CO and NE is running or create a real CO

 

 

Expected Result

1. NMS support to browse chassis inventory inside CO

2. User can check chassisPhysicalID information.

 

1. NMS support to browse chassis inventory inside CO

2. The chassis id from inventory is matched with chassis id from blade.

(Notice: The chassis id from inventory is in Hex format, the chassis id from blade is in Dec format)

 

阅读(3287) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~