Open
Bug 532913
Opened 16 years ago
Updated 16 years ago
[XML-RPC] TestCase.unlink_plan: Last unlink deletes TestCase also if TestPlan ID is wrong
Categories
(Testopia :: API, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: nuabaranda, Assigned: gregaryh)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: 2.3
The XML-RPC function TestCase.unlink_plan does not only unlink the TestCase from the given TestPlan but from all TestPlans thus removing it!
Reproducible: Always
Steps to Reproduce:
1. Have a TestCase linked to 2 different TestPlans.
2. Try unlinking it from one TestPlan.
Actual Results:
2. TestCase is unlinked from both TestPlans.
Expected Results:
2. TestCase is just unlinked from mentioned TestPlan.
| Reporter | ||
Updated•16 years ago
|
Severity: critical → blocker
| Assignee | ||
Comment 1•16 years ago
|
||
I am unable to reproduce this. Unlinking from a single plan only unlinks it from that plan. Can you give me any more details as to what you were doing?
| Reporter | ||
Updated•16 years ago
|
Summary: [XML-RPC] TestCase.unlink_plan unlinks from ALL plans → [XML-RPC] TestCase.unlink_plan: Last unlink deletes TestCase also if TestPlan ID is wrong
| Reporter | ||
Comment 2•16 years ago
|
||
(In reply to comment #1)
> I am unable to reproduce this. Unlinking from a single plan only unlinks it
> from that plan. Can you give me any more details as to what you were doing?
At first, sorry, the bug description was faulty due to a bug in my TestCase. Here comes the real problem:
When runing unlink_plan for a TestCase which is only linked to one last TestPlan and providing a wrong TestPlan ID (one, where the TestCase is not linked to), the TestCase gets unlinked from its last TestPlan (whose ID was not provided!) and thus deleted. I would expect an error message when providing an invalid TestPlan ID as this is clearly a fault of the user!
| Reporter | ||
Updated•16 years ago
|
Severity: blocker → critical
You need to log in
before you can comment on or make changes to this bug.
Description
•