mysql cluster 性能测试之响应时间测试用例, 请大家指导, 万分感谢!

Item Total:3

Case Total:10

Item Code:	testitem1784579
path:	Library FolderèMedia SwitchèSTèRollingStream2.6.0èDRMèSecure LS DB ClusterèèMYSQL CLUSTER response time
Item Name:	[01]  MYSQL CLUSTER response time
Case Count:	10	Create Time:	2007-03-07 08:00:36.0	Index Code:	01
Item Status:	null	Create By:	meil.xu
Test Preset Condition:
N/A
Item Description:
N/A

Item Code:	testitem1784580
path:	Library FolderèMedia SwitchèSTèRollingStream2.6.0èDRMèSecure LS DB ClusterèèMYSQL CLUSTER response time
Item Name:	[01]  MYSQL CLUSTER response time ---Function test case
Case Count:	5	Create Time:	2007-03-07 08:01:34.0	Index Code:	01
Item Status:	null	Create By:	meil.xu
Test Preset Condition:
N/A
Item Description:
N/A

Path	MYSQL CLUSTER response time ---Function test case->Insert a record to mysql cluster, check response time
Headline:	Insert a record to mysql cluster, check response time
Index Code:	01	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:01:34.0	Creator:	meil.xu
Test Purpose:	Insert a record to mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to insert data for each table mysql> INSERT INTO subscriber VALUES ('100002','100002','passwd',1,'A','A','Meil1-100002','0','0','a','0','0' ); * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> INSERT INTO subscriber VALUES ('100002','100002','passwd',1,'A','A','Meil1-100002','0','0','a','0','0' ); Query OK, 1 row affected (0.06 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Function test case->Update records of mysql cluster, check response time
Headline:	Update records of mysql cluster, check response time
Index Code:	02	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:01:36.0	Creator:	meil.xu
Test Purpose:	Update records of mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to update data for each table mysql> update schedule set add_date ='20070906' where schedule_id = '1000001'; first update the middle record,then try the foregoing record, at last try the latter record * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.5sec mysql> update schedule set add_date ='20070906' where schedule_id = '1000001'; Query OK, 1 row affected (0.21 sec) Rows matched: 1 Changed: 1 Warnings: 0 CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Function test case->Delete records of mysql cluster, check response time
Headline:	Delete records of mysql cluster, check response time
Index Code:	03	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:01:37.0	Creator:	meil.xu
Test Purpose:	Delete records of mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to delete data for each table use primary key mysql> delete from subscriber where drm_subscriber_id ='80005'; first the middle record,then try the foregoing record, at last try the latter record * do the upper operations use other key if have * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> delete from subscriber where drm_subscriber_id ='80005'; Query OK, 1 row affected (0.02 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Function test case->Select a record to mysql cluster, check response time
Headline:	Select a record to mysql cluster, check response time
Index Code:	04	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:01:39.0	Creator:	meil.xu
Test Purpose:	Select a record to mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to delete data for each table use primary key mysql> select * from subscriber where drm_subscriber_id= '999789'; first the middle record,then try the foregoing record, at last try the latter record * do the upper operations use other key if have * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> select * from subscriber where drm_subscriber_id= '999789'; Empty set (0.01 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Function test case->Select records of a range from mysql cluster, check response time
Headline:	Select records of a range from mysql cluster, check response time
Index Code:	05	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:01:41.0	Creator:	meil.xu
Test Purpose:	Select records of a range from mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to delete data for each table use primary key mysql> select * from schedule where schedule_id like '100094%'; mysql> select * from schedule where schedule_id like '%094%'; mysql> select * from schedule where schedule_id like '94%'; first the middle record,then try the foregoing record, at last try the latter record * do the upper operations use other key if have * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> select * from schedule where schedule_id like '100094%'; 11 rows in set (0.05 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Item Code:	testitem1784586
path:	Library FolderèMedia SwitchèSTèRollingStream2.6.0èDRMèSecure LS DB ClusterèèMYSQL CLUSTER response time
Item Name:	[02]  MYSQL CLUSTER response time ---Abnormal case
Case Count:	5	Create Time:	2007-03-07 08:03:56.0	Index Code:	02
Item Status:	null	Create By:	meil.xu
Test Preset Condition:
N/A
Item Description:
N/A

Path	MYSQL CLUSTER response time ---Abnormal case->Insert an invalid record to mysql cluster, check response time
Headline:	Insert an invalid record to mysql cluster, check response time
Index Code:	01	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:03:56.0	Creator:	meil.xu
Test Purpose:	Insert an invalid record to mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to insert data for each table mysql> INSERT INTO subscriber VALUES ('100002','100002','passwd',1,'A','A','Meil1-100002','0','0','a','0','0' ); * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> INSERT INTO subscriber VALUES ('100002','100002','passwd',1,'A','A','Meil1-100002','0','0','a','0','0' ); Query OK, 1 row affected (0.06 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Abnormal case->Update an inexistent record of mysql cluster, check response time
Headline:	Update an inexistent record of mysql cluster, check response time
Index Code:	02	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:03:58.0	Creator:	meil.xu
Test Purpose:	Update a inexistent record of mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to update data for each table mysql> update schedule set add_date ='20070906' where schedule_id = '1000001'; first update the middle record,then try the foregoing record, at last try the latter record * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.5sec mysql> update schedule set add_date ='20070906' where schedule_id = '1000001'; Query OK, 1 row affected (0.21 sec) Rows matched: 1 Changed: 1 Warnings: 0 CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Abnormal case->Delete an inexistent of mysql cluster, check response time
Headline:	Delete an inexistent of mysql cluster, check response time
Index Code:	03	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:04:00.0	Creator:	meil.xu
Test Purpose:	Delete records of mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to delete data for each table use primary key mysql> delete from subscriber where drm_subscriber_id ='80005'; first the middle record,then try the foregoing record, at last try the latter record * do the upper operations use other key if have * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> delete from subscriber where drm_subscriber_id ='80005'; Query OK, 1 row affected (0.02 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Abnormal case->Select an inexistent record to mysql cluster, check response time
Headline:	Select an inexistent record to mysql cluster, check response time
Index Code:	04	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:04:02.0	Creator:	meil.xu
Test Purpose:	Select an inexistent record to mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to delete data for each table use primary key mysql> select * from subscriber where drm_subscriber_id= '999789'; first the middle record,then try the foregoing record, at last try the latter record * do the upper operations use other key if have * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> select * from subscriber where drm_subscriber_id= '999789'; Empty set (0.01 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A

Path	MYSQL CLUSTER response time ---Abnormal case->Select an inexistent record of a range from mysql cluster, check response time
Headline:	Select an inexistent record of a range from mysql cluster, check response time
Index Code:	05	Test Type:	ST	Version:	1
Case Priority:	high	Case Severity:	high	Estimated Effort:	null
Review Status:	none	Create Time:	2007-03-07 08:04:03.0	Creator:	meil.xu
Test Purpose:	Select an inexistent record of a range from mysql cluster, check response time
Test Step:	* use mysql monitor connect to mysql cluster * use sentence like following to delete data for each table use primary key mysql> select * from schedule where schedule_id like '100094%'; mysql> select * from schedule where schedule_id like '%094%'; mysql> select * from schedule where schedule_id like '94%'; first the middle record,then try the foregoing record, at last try the latter record * do the upper operations use other key if have * repeat above opereations for at least 3 times
Test Preset Condition:	DRM work normally there are data about at least 100000 users in databases there are a lot of clients using database, doing updade, select ,insert, delete etc. If without , you can use simulator to do it.
Expect Result:	the response time is below 0.1 sec mysql> select * from schedule where schedule_id like '100094%'; 11 rows in set (0.05 sec) CPU MEM IO is normal
Test Result:	N/A
Remark	N/A