Bug 844946 - [CaseRuns] "Communication with server got some unknow errors" and bad UI
Summary: [CaseRuns] "Communication with server got some unknow errors" and bad UI
Keywords:
Status: VERIFIED
Alias: None
Product: TCMS
Classification: Other
Component: Web UI
Version: 3.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.8.0
Assignee: June Zhang
QA Contact: Nobody
URL:
Whiteboard:
: 844844 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-01 10:30 UTC by jihu
Modified: 2022-03-14 03:26 UTC (History)
7 users (show)

Fixed In Version: 3.8.0-3
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
case run error (153.04 KB, image/png)
2012-08-01 10:33 UTC, jihu
no flags Details

Description jihu 2012-08-01 10:30:38 UTC
Description of problem:
When clicking caserun summary,page will diaplay a error box.

Version-Release number of selected component (if applicable):
TCMS 3.8.0 on stage

How reproducible:
100%

Steps to Reproduce:
1.open a test plan which have some cases 
2.enter a case page which belong to one or more run
3.click "Case Runs"lable
4.click the triagle on front of plan to expand the run list
5.click one run sumary 
  
Actual results:
Page pop up a box with "Communication with server got some unknow errors",after clicking the "ok"button on box,it display bad ui.

Expected results:
Page shuould display normally.

Additional info:

Comment 1 jihu 2012-08-01 10:33:32 UTC
Created attachment 601704 [details]
case run error

Comment 2 Zheng Liu 2012-08-02 01:53:37 UTC
This bug has been fixed.

Comment 3 Xin Gao 2012-08-03 02:21:04 UTC
*** Bug 844844 has been marked as a duplicate of this bug. ***

Comment 4 Xin Gao 2012-08-03 07:02:18 UTC
Verify 3.8.0-3 on stage -->PASS

Verify steps:
1.open a test plan which have some cases 
2.enter a case page which belong to one or more run
3.click "Case Runs"lable
4.click the triagle on front of plan to expand the run list
5.click one run sumary 

Actual result:
work well now.


Note You need to log in before you can comment on or make changes to this bug.