On Tue, Oct 24, 2023 at 9:48 AM Naomi Ibe <naomi.ibeh69@xxxxxxxxx> wrote: > > I'm Ibe Naomi Amarachi,I'm a Nigerian and I currently live in > Lagos,Nigeria. I'm a graduate of the African Leadership Xcelerator > Software Engineering program (ALX SE), with specialization in backend > web development and I'm applying for the "Moving Existing Tests to a > Unit Testing Framework" project > > Some of my projects that involve working with Shell,C and Git can be found here: > > https://github.com/Amarajah/alx-system_engineering-devops > > https://github.com/Amarajah/alx-low_level_programming > > Git has been a part of my software engineering journey from day one > and it's allowed me to collaborate with peers and also keep track of > my personal projects. Currently Git uses end-to-end tests for error > conditions that could easily be captured by unit tests, the project is > aimed at turning end-to-end tests to unit tests, and I'd love to be a > part of it Maybe a period is missing at the end of the above sentence. Otherwise Ok. > My microproject contribution is here: > > https://public-inbox.org/git/20231009011652.1791-1-naomi.ibeh69@xxxxxxxxx/T/#u > > And here is my updated contribution link after review by the Git community: > > https://public-inbox.org/git/xmqqttqox5cp.fsf@gitster.g/T/#u It could help to say if your contribution has been merged to 'master', 'next', 'seen' or not at all. > Below is my project timeline: > (Of course I'd be very much willing to work with the community and > mentors to edit it so it perfectly meets up to the community's > expectations) > > October 2, 2023 - October 30, 2023 > > Familiarizing myself with the community , mailing list and > contributing my microproject > > November 20, 2023 - December 4, 2023 > > Familiarizing myself with the already existing tests and also the > chosen unit test framework > > Do more research on the internship projects and find better ways to > get it done in harmony with coding guidelines and community > requirements > > December 4, 2023 - December 31, 2023 > > First document the initial state of the test files, then make sure all > test files conform to coding guidelines down to the tiniest details > (e.g git/t/helper/test-write-cache.c and git/t/helper/test-advise.c > have die() messages which do not conform to coding guidelines) We don't advise spending a lot of time during your internship with small things that could be part of someone else's microproject later. You should be focused on the internship goal first. Of course if you are migrating some code to the new unit test framework, it's Ok to improve that code before migrating it. But no need to improve everything under t/helper before starting to migrate parts of the code there. I think that one of the important tasks to be done early is to identify what code in t/helper is unit testing C code and what code is really about helping other tests in the t/t*.sh scripts. It would be nice if you could give an example of each kind of code. > January 2, 2024 - January 31, 2024 > > Run the tests and verify they still work as originally intended > > Begin migrations of test files > > Test migrated files and make necessary changes based on feedback > received from teammates and mentors An example of how you would migrate parts of a test, or how a migrated test would look like, would be nice. > February 1, 2024 - March 1, 2024 > > Continue testing migrated files and making necessary changes based on > feedback received from teammates and mentors > > Document each step and request for reviews from teammates and mentors > > Tidy up the project,make sure all necessary files are migrated, they > all work as intended, they are well documented and that there are no > conflicts Thanks, Christian.
