Difference between revisions of "Fedpkg Test Suite"
(→Project Details) |
|||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Fedpkg Test Suite == | == Fedpkg Test Suite == | ||
| − | + | Testing fedpkg using unittest. | |
== Project Description == | == Project Description == | ||
| − | + | fedpkg is a component within Fedora Packager. It is a python library and cli front end for managing Fedora packages within Fedora's git system. The project is testing fedpkg library using nose unittest frameworks. | |
== Project Leader(s) == | == Project Leader(s) == | ||
| − | + | [http://zenit.senecac.on.ca/wiki/index.php/User:SaadHusain Saad Husain] | |
| + | |||
| + | [http://zenit.senecac.on.ca/wiki/index.php/User:zwang98 Zhiqing Wang] | ||
== Project Contributor(s) == | == Project Contributor(s) == | ||
| Line 19: | Line 21: | ||
== Project Details == | == Project Details == | ||
| − | + | *First we need get familiar with fedpak and nose | |
| + | *fedpak is built on GIT, which, in turn, is an alternative to CVS. So we better gain certain level of knowledge how these programs work | ||
| + | *Python is the key to this project. As Luke suggested, the testing code should be embedded inside fedpkg. | ||
| + | **Get speed on Python | ||
| + | **Read the source code of fedpkg | ||
| + | **Go through the sample test cases | ||
| + | *When we get to this stage, it will be writing and rewriting the test code to get the meaningful test results. | ||
== Project Plan == | == Project Plan == | ||
| Line 25: | Line 33: | ||
Goals for each release: | Goals for each release: | ||
* 0.1 | * 0.1 | ||
| + | Use nose testing some simple python programs. The programs should be our own. | ||
* 0.2 | * 0.2 | ||
| + | Each of the members will write a test for a python library function in fedpkg. The test must show some meaningful results. | ||
* 0.3 | * 0.3 | ||
| + | Either improve the test from the second stage or write more test for other library functions in fedpkg. | ||
== Project News == | == Project News == | ||
| − | + | * 2010-10-15 - [[fedpkg Tests - Meeting with Jesse Keating and Luke Macken 2010-10-15]] | |
| − | |||
| − | |||
Latest revision as of 11:39, 17 October 2010
Contents
Fedpkg Test Suite
Testing fedpkg using unittest.
Project Description
fedpkg is a component within Fedora Packager. It is a python library and cli front end for managing Fedora packages within Fedora's git system. The project is testing fedpkg library using nose unittest frameworks.
Project Leader(s)
Project Contributor(s)
Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki
NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.
Project Details
- First we need get familiar with fedpak and nose
- fedpak is built on GIT, which, in turn, is an alternative to CVS. So we better gain certain level of knowledge how these programs work
- Python is the key to this project. As Luke suggested, the testing code should be embedded inside fedpkg.
- Get speed on Python
- Read the source code of fedpkg
- Go through the sample test cases
- When we get to this stage, it will be writing and rewriting the test code to get the meaningful test results.
Project Plan
Goals for each release:
- 0.1
Use nose testing some simple python programs. The programs should be our own.
- 0.2
Each of the members will write a test for a python library function in fedpkg. The test must show some meaningful results.
- 0.3
Either improve the test from the second stage or write more test for other library functions in fedpkg.
