Skip to content
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

Open
danigm opened this issue Jan 3, 2024 · 6 comments
Open

Improve test coverage in rpmlint #204

danigm opened this issue Jan 3, 2024 · 6 comments
Labels
Medium Sized Project Medium sized project is 175 hours rpmlint

Comments

@danigm
Copy link

danigm commented Jan 3, 2024

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

@ddemaio ddemaio added rpmlint Medium Sized Project Medium sized project is 175 hours Larged Sized Project Large sized project is 350 hours labels Jan 9, 2024
@ddemaio ddemaio removed the Larged Sized Project Large sized project is 350 hours label Jan 16, 2024
@Vashi1
Copy link

Vashi1 commented Jan 19, 2024

Hi @danigm, I'm a computer science student at a research institution in Asia.
I have been coding in Python for around 4 years now, I'm interested in contributing to OSS and this project interests me and I believe it will help me to kickstart my open-source journey.

I read through the project description and I got a gist of it, Can you guide me on getting started with this project?

Regards,
aarvee

@danigm
Copy link
Author

danigm commented Jan 23, 2024

Hi @danigm, I'm a computer science student at a research institution in Asia. I have been coding in Python for around 4 years now, I'm interested in contributing to OSS and this project interests me and I believe it will help me to kickstart my open-source journey.

I read through the project description and I got a gist of it, Can you guide me on getting started with this project?

Regards, aarvee

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 pytest.

@Vashi1
Copy link

Vashi1 commented Feb 25, 2024

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,
aarvee

@danigm
Copy link
Author

danigm commented Feb 26, 2024

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?

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.

@HafsaParker
Copy link

hi @danigm
I am Hafsa Parker, a software Engineer, and I am interested in this project for GSOC. Can you guide me through how I can contribute and make my chances of being selected this year?
Kind Regards,
Hafsa Parker

@danigm
Copy link
Author

danigm commented Mar 5, 2024

hi @danigm I am Hafsa Parker, a software Engineer, and I am interested in this project for GSOC. Can you guide me through how I can contribute and make my chances of being selected this year? Kind Regards, Hafsa Parker

Hello! in the previous comments you have the steps to follow:

  1. Get the source code, install dependencies and run the current test suite: Improve test coverage in rpmlint #204 (comment)
  2. Look for some task to do: Improve test coverage in rpmlint #204 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Medium Sized Project Medium sized project is 175 hours rpmlint
Projects
None yet
Development

No branches or pull requests

4 participants