-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve test coverage in rpmlint #204
Comments
Hi @danigm, I'm a computer science student at a research institution in Asia. I read through the project description and I got a gist of it, Can you guide me on getting started with this project? Regards, |
The first thing to do is to be able to run the current test suite from the source code. For that you will need a Linux OS, in a real machine or a virtual machine. I suggest to install openSUSE Tumbleweed, but any modern linux will work. Get the source code and install the dependencies in the system. After that you can just run the test suite with |
Hi @danigm, I've gotten rpmlint installed and running on my system, also I've studied how software testing works and learned using unittests and pytests. Can you guide me on what to do next to get started with this project? Thanks, |
If you have the rpmlint code from github and all dependencies and you can run "pytest" correctly, now it's time to try to modify something. We've some issues in the github project with the label "help wanted", you can take a look to them and try to find something simple to do. Fork the repository, create a branch and you can start to work. Don't hesitate to create a draft Pull Request and ask me there, I could review the code and help a bit more. The big tasks related to the GSoC are rpm-software-management/rpmlint#1105 and rpm-software-management/rpmlint#1104. You can always take a look to the project and look for something simple to improve. There are a lot of old issues and maybe there's something there that can be fixed, or maybe create new tests to improve code coverage or some reported issue that's not been tested. |
hi @danigm |
Hello! in the previous comments you have the steps to follow:
|
Project Title: Improve test coverage in rpmlint
Description: The rpmlint project has a lot of tests. The past year during the GSoC we extend the test tools to make it easy to write tests mocking rpm files, but there are still a lot of tests that uses binary rpm files for tests.
The goal of this project is to try to reduce the number of binary .rpm files in the repository and replace tests with mock and extend the test suite to increase the code coverage.
Deliverable: The result of this project will be multiple pull requests to the rpmlint repository with new tests.
Mentor: @danigm
Communication channels:
Be patient and wait one or two days before reping, I'll try to answer as soon as possible, but it's not always possible answer in the same day.
Skills: python, RPM, packaging, git, Linux
Skill Level: Medium/Hard
Get started:
Links
FakePkg
s to use in different tests rpm-software-management/rpmlint#1104The text was updated successfully, but these errors were encountered: