Bug 1127139
| Summary: | [test case] user can create new run when estimated_time is null, while can not create new case when estimated_time is null | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] TCMS | Reporter: | yangqiu <qiyang> | ||||
| Component: | Application | Assignee: | Yang Ren <ryang> | ||||
| Status: | VERIFIED --- | QA Contact: | Nobody <nobody> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.8.10 | CC: | cqi, junzhang, leiwang, ryang, vchen | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
The issue also happened when invoke TestCase.create to create case without cc, system will return 400 error as follow:
In [25]: case1 = {
'category': 357,
'product': 243,
'summary': 'qiyang test case 111',
'priority': 1,
'script': 'qiyang test script',
}
Fault: <Fault 400: ['Invaild estimated_time format.']>
while the document for xmlrpc define the estimated_time is Optional.
estmiated_time is required in WEBUI, but not required in XMLRPC api. This is origin design. As to "Fault: <Fault 400: ['Invaild estimated_time format.']>", need fix in this version. Now the estimated_time is null-able in create page. verify on devel server with tcms3.8.10-1------>pass verify steps are the same as the description. Both test case and test run can be created with the estimated time is null. and the format in xmlrpc api is like 00:00:00 |
Created attachment 924409 [details] [test case] user can create new run when estimated_time is null, while can not create new case when estimated_time is null Description of problem: as summary. Version-Release number of selected component (if applicable): v3.8.10-1 on devel server. How reproducible: 100% Steps to Reproduce: 1.user create a run when estimated_time is null. 2.user create a case when estimated_time is null. Actual results: for step 1: user can save the new run with estimated_time as 0m. for step 2: user can not save the new case, system will show warning: estimated_time is required. Expected results: user can create run and case when estimated_time is null. Additional info: