Entradas

GSoC: End of the project

Imagen
  Hi there!👋 This is the last week of coding for the Google Summer of Code project. 😞 During all this time, I have learned to work with the rpmlint environment and many aspects that I did not know before.    What I have done... 🙋 Below, I will summarize a little bit of the work done during this time.  During the first few weeks dedicated to the Google Summer of Code project, I've been familiarizing myself with the rpmlint environment. I learned about all the different tests in rpmlint, contacting the codebase to get a better understanding of the whole project. Once the coding period began, I started replacing the existing binary rpm in the tests with FakePkg, previously finding the smallest or easiest to replace packages to begin with. Once the simpler tests were replaced, I continued with the replacement of more complex tests, with a deep understanding of rpm packages and the current test in rpmlint. At the same time as replacing the binaries, I refactored the tests, moving com

GSoC: 10 weeks

Imagen
Hi! This is the tenth week of the Google Summer of Code project. There are only a few weeks left until the end of the course.  Since the last blog post, I've managed to replace all the binary packages in the simplest tests, and I've started with some of medium difficulty. These are the following, with some notes of what each one requires:  test_erlang.py (require binary files) test_shlib_policy.py (require binary files) test_logrotate.py (special file content & permissions) test_lib_dependency.py (Just one test needed, Link to .so shouldn't be present in devel package) test_icon_sizes.py (Lots of image binary files, just checks paths and image size) test_files.py (Lots of tests, but easy to replace just replicating rpm files and the content) test_doc.py (files, permissions and requirements. Files with RPMFILE_DOC flag) test_bashisms.py (just file content, it could require some tweaks in the second test, related to pkg.dirname) Up to this point, I've replaced half of

GSoC: 7 weeks

Imagen
  Hi! It's already been 7 weeks since the Google Summer of Code programming period began. During this time, I have been getting familiar with the project environment and understanding how it works.😁 My mentor has classified the tests into three levels based on difficulty: easy, medium, and hard. Up until this point, I've been working on the simplest tests, which are as follows: test_sysvinitonsystemd.py  test_pam_modules.py  test_pkgconfig.py  test_menuxdg.py  test_LSB.py  test_FHS.py  test_dbus_policy.py  test_appdata.py  test_build_root.py  test_mixed_ownership.py I have managed to replace all of them, except for the last two. By next week, I hope to be able to finish them and be able to start with the medium difficulty ones. See you very soon!✌

GSoC: Week 3-4

Imagen
  Hello!! I am back again with another GSoC report. In this blog post I will share what I worked on the 3rd and 4th week of Google Summer of Code!😄 After talking to my mentor, we decided to replace the simpler-looking binary files with FakePkg with metadata and files, similar to how I discussed in the previous post, to leave the more complicated ones for last.  Therefore, some of these files are: - test_sysvinitonsystemd  - test_pam_modules  - test_pkgconfig  - test_menuxdg  - test_mixed_ownership  - test_LSB  Looking ahead to the next few weeks, the goal is to focus on the development of more complex tests, so if you are interested don't miss the following blog posts!  See you soon!👋

GSoC: Week 1-2

Imagen
  Hello again! It's been two weeks since the GSoC coding period officially began. 😊 The first week was mainly spent familiarizing myself with the rpmlint environment and establish a first contact with my mentor. After two sessions with my mentor, the first task to be carried out will be to replace binary rpm (located in test/binary), which are used only to test simple functions, with FakePkg with metadata and files. This way, it is possible to remove the number of binaries and it will be easier to understand what the tests are doing. An example is shown below: For example, in the "test_tmp_files.py" file we initially find the following code: and after modifying it, it will be as follows: The content of "TMPFILES" has been defined in a mock file to show greater readability and clarity in the code: As you can see, I have to make use of this helper function "get_tested_mock_package", defined in the "Testing.py" file: This is what I have been do

GSoC: Improve test coverage in rpmlint. Presentation

Imagen
Hi there!👋 I'm Luz Marina, a third-year student of Computer Engineering, who would like to learn as much as possible about the different branches covered by this career for my professional future. About me 👤 So you can get to know a little bit about me, m y interest in this career arose during compulsory secondary education, where I had a computer science subject. Apart from what I am taught in my degree, thanks to the wide range of online educational resources, such as courses, tutorials and online communities, I try to expand my knowledge and skills in different areas of computer science. In addition, I consider myself a person with teamwork skills. Currently 🔛 This year, I've been selected for the GSoC to work with OpenSuse Tumbleweed linux.  The main goal of the project is to reduce the number of .rpm binaries in the repository and replace the tests with mocks and extend the test suite to increase code coverage. In addition, an improvement of the tests and correction of