Bug 654445

Summary:	Automated testing coverage for lvm2app
Product:	[Fedora] Fedora	Reporter:	Petr Rockai <prockai>
Component:	lvm2	Assignee:	Petr Rockai <prockai>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	19	CC:	agk, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, msnitzer, prajnoha, prockai
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:	2014-09-10 16:53:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Petr Rockai 2010-11-17 21:21:17 UTC

We currently do not run automated coverage for lvm2app. This needs to be fixed. This BZ should cover both adapting the existing test code for automated running, integrating the testing with make check/buildbot and adding new test cases.

Comment 1 Petr Rockai 2010-11-17 21:21:36 UTC

In progress.

Comment 2 Petr Rockai 2010-12-12 23:05:13 UTC

The basic framework for this is in, and is passing on the buildbots. We need a bit more automation (making the tests easier to write) as well as more coverage (we only have very rudimentary stuff right now).

Comment 3 Fedora End Of Life 2013-04-03 20:13:20 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 Petr Rockai 2014-09-10 16:53:35 UTC

This was addressed a while back, cf. test/api. The coverage is small, but better than nothing. Extending (or reworking) this will be, presumably, part of the long-term liblvm effort.