Watching the latest updates in Fedora, there have been many items (libtiff, wireshark, asterisk, etc.) which I know how to use, but I am somewhat hesitant to test since they require having a lot of sample files, configurations, and (in the case of things like Asterisk) other systems to talk to.
And while Bugzilla often tells us the exact format(s) and protocol(s) fixed by a release, the particular items needed to test it are hard to predict in advance.
Does the Fedora test team or a related project have a library of configuration and test files of various types which may be downloaded for testing purposes? If not perhaps we should create one. Making setups and sample items on the fly using software other than that under test can take me a lot of time.
--- SJG
On Tue, 2011-04-26 at 22:48 -0400, Samuel Greenfeld wrote:
Watching the latest updates in Fedora, there have been many items (libtiff, wireshark, asterisk, etc.) which I know how to use, but I am somewhat hesitant to test since they require having a lot of sample files, configurations, and (in the case of things like Asterisk) other systems to talk to.
And while Bugzilla often tells us the exact format(s) and protocol(s) fixed by a release, the particular items needed to test it are hard to predict in advance.
Does the Fedora test team or a related project have a library of configuration and test files of various types which may be downloaded for testing purposes? If not perhaps we should create one. Making setups and sample items on the fly using software other than that under test can take me a lot of time.
Not that I'm aware of, but if you come across any, it seems straightforward to add these to the wiki as test cases (with file(s) attached). If placed in the proper category (e.g. Category:Package_asterisk_test_cases]]), the test cases will be presented in the bodhi update as sample tests to run.
Thanks, James
On 04/26/2011 10:48 PM, Samuel Greenfeld wrote:
<snip>
Does the Fedora test team or a related project have a library of configuration and test files of various types which may be downloaded for testing purposes? If not perhaps we should create one. Making setups and sample items on the fly using software other than that under test can take me a lot of time.
Really needed! The current test cases work well, but most of the packages held for security testing and critical path testing do not have test cases with necessary files.
Some developers/packagers do have test files, but it is hard to find them. Maybe one of the excellent Fedora or Red Hat gurus could come up with a way to collect them, organize them and put them on a server somewhere. I know, maintenance would be difficult, but then maybe it could be automated as a byproduct of packaging and updating the packages. Just a thought.
Personally I was thinking the file library probably should be a separate structure from the test cases. While configuration files may be package-specific, sample graphic and sound files may be usable by more than one application.
Copyright guidelines on what is and is not allowed in this library also would have to be created if the wiki doesn't have these already. A quick glance suggests that many Image files in the Fedora wiki do not have Wikipedia-style licensing tags, so I don't know what documentation approach is desired.
On Wed, Apr 27, 2011 at 11:28 AM, Clyde E. Kunkel clydekunkel7734@cox.netwrote:
On 04/26/2011 10:48 PM, Samuel Greenfeld wrote:
<snip>
Does the Fedora test team or a related project have a library of configuration and test files of various types which may be downloaded for testing purposes? If not perhaps we should create one. Making setups
and
sample items on the fly using software other than that under test can
take
me a lot of time.
Really needed! The current test cases work well, but most of the packages held for security testing and critical path testing do not have test cases with necessary files.
Some developers/packagers do have test files, but it is hard to find them. Maybe one of the excellent Fedora or Red Hat gurus could come up with a way to collect them, organize them and put them on a server somewhere. I know, maintenance would be difficult, but then maybe it could be automated as a byproduct of packaging and updating the packages. Just a thought.
-- Regards, OldFart
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test