Bug 869594 - Implement CasePlan container (with support for sortkey)
Summary: Implement CasePlan container (with support for sortkey)
Alias: None
Product: Fedora
Classification: Fedora
Component: python-nitrate
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Petr Šplíchal
QA Contact: Fedora Extras Quality Assurance
Depends On: 729233
Blocks: 869566
TreeView+ depends on / blocked
Reported: 2012-10-24 11:29 UTC by Petr Šplíchal
Modified: 2016-06-01 01:44 UTC (History)
3 users (show)

Fixed In Version: python-nitrate-1.0-0.fc20
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2014-05-18 22:53:43 UTC

Attachments (Terms of Use)

Description Petr Šplíchal 2012-10-24 11:29:32 UTC
Description of problem:

As bug 729233 has been fixed we could now add a new CasePlan
container with the support for getting/setting the sort order of
test case in test plan. This should probably work similarly as the
CaseRun class which connects test cases with test runs.

Comment 1 Petr Šplíchal 2014-03-23 00:21:01 UTC
Support for test case sortkey in test plans [BZ#869594]
New classes CasePlan and PlanCasePlans implemented
Method TestPlan.sortkey() for getting/setting the order


Comment 2 Fedora Update System 2014-04-11 15:25:26 UTC
python-nitrate-1.0-0.fc20 has been submitted as an update for Fedora 20.

Comment 3 lnie 2014-04-15 04:11:15 UTC
python-nitrate-1.0-0.fc20 works

Comment 4 Fedora Update System 2014-04-15 15:36:28 UTC
Package python-nitrate-1.0-0.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-nitrate-1.0-0.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2014-05-18 22:53:43 UTC
python-nitrate-1.0-0.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

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