[JdeRobot] GSoC'25 Project #2: Robotics Academy CI & Testing Inquiry

Abdallah Ibrahim abdallah.ibrahim5115 at gmail.com
Fri Apr 4 11:48:45 CEST 2025


Dear Pedro,

Thanks for your review.
I have added the stated changes and updated my draft proposal in the GSOC
portal. Let me know if you think anything is missing or can be improved.

I have one additional question: Do you have any specific tests or
high-priority testing areas in mind for the Robotics Infrastructure (RI)
repository?

Thank you again for your guidance, and I look forward to your feedback.

Best regards,

...


On Mon, Mar 31, 2025 at 10:28 AM Pedro Arias Perez <pedro.ariasp at upm.es>
wrote:

> Dear Abdallah Ibrahim,
>
> Please consider the following changes for your proposal:
>
>    - Add a table/list with your contributions to JdeRobot repositories
>    and link to them.
>    - Be more specific with the proposed deliverables and add their
>    deadline date in the timeline.
>    - Add a "Why me?" and "Why JdeRobot?" sections.
>
> Additionally, we do not mind delaying the schedule two weeks, and start
> working when your exams are over. However, I do think it will be good to
> hold weekly meetings during that time (and probably tiny tasks as well) to
> get things moving.
>
> Best regards,
> Pedro
>
>
> El 30/3/25 a las 20:53, Abdallah Ibrahim escribió:
>
> Dear Pedro,
>
> Thanks for your feedback.
>
> I wanted to let you know that I have submitted my draft proposal in the
> GSOC portal. I appreciate your guidance and look forward to your detailed
> feedback.
> Any additional suggestions on the deliverables or specific focus areas
> would be greatly appreciated.
>
> Thank you for your time and support.
>
> Best regards,
>
> On Sat, Mar 29, 2025 at 2:48 PM Pedro Arias Perez <pedro.ariasp at upm.es>
> wrote:
>
>> Dear Abdallah Ibrahim,
>>
>> Thank you for your interest in JdeRobot and in project we are mentoring.
>>
>> You understood it correctly. We aim to cover RAM, RI and RA repositories,
>> but we can focus on one or two of them if needed. About your questions:
>>
>> There is no testing setup or previous efforts. So, the existing approach
>> is none. We have to built it and we can choose the methodology that better
>> aligns with Robotics Academy and with us. To be 100% honest, we had an
>> intern exploring Selenium testing, but afaik it is discontinued.
>>
>> I strongly believe that we better do a fresh start. We mentors have
>> previous experience building CI pipelines, so you will be guided anytime. I
>> do like your pipeline proposal. But before unit testing, I suggest to start
>> with linting, docstrings and copyright (or other basic similar tests).
>>
>> I have seen that you already filled the web form and finished the
>> mandatory challenges, well done. Feel free to share with us your draft
>> proposal. We can guide you with some deeper feedback.
>>
>> Lastly, since the arrival of chatGPT, we are valuing contributions to
>> JdeRobot repositories more than the past years. Then, my advice would be to
>> keep working on the RoboticsAcademy repositories; open issues and fixing
>> them via pull request to significantly increase your chances to be
>> selected. Even contributions to the documentation page is valuable.
>>
>> Best regards,
>> Pedro
>> El 29/3/25 a las 9:42, Abdallah Ibrahim escribió:
>>
>> Greetings,
>>
>> I hope you are doing well.
>>
>> My name is Abdallah Ibrahim Ismail, an undergraduate computer science
>> student at Ain Shams University in Egypt. I am very excited about the
>> opportunity to apply for GSoC under JdeRobot for Project #2: Robotics
>> Academy CI & Testing.
>>
>> As I work on my proposal, I would appreciate your guidance to ensure that
>> my plan is well aligned with the project’s objectives. I understand that
>> the goal is to develop automated testing and CI pipelines for the RAM, RI,
>> and RA repositories. While I feel confident about the CI side, I have a few
>> questions regarding the testing strategy:
>>
>> *Scope & testing focus*:
>> What types of tests would you prioritize for these repositories? My
>> initial thought is to work in an agile manner, starting with a core unit
>> testing setup for each repo, then moving on to integration tests, and
>> eventually covering end-to-end tests if feasible.
>>
>> *Current testing setup & previous efforts*:
>> Could you please point me to any prior efforts or the current testing
>> approach and setups within the RAM, RI, or RA repositories?
>>
>> If you have any additional insights or recommendations that could help
>> refine my proposal, I would greatly appreciate your input.
>>
>> Thank you very much for your time and support.
>>
>> Best regards,
>>
>> --
>> *Abdallah Ibrahim Ismail*
>> GitHub Profile
>> <https://urldefense.com/v3/__https://github.com/Apolo151__;!!D9dNQwwGXtA!X2cndMVKjcJZvViZc97OKfdFlf0AiMvrlvskjNibA8OZiU6zk9kumtPdj2BoU1yQizQqxAGApt0uQpw8Fe-tyCwrlCUo$>
>> LinkedIn Profile
>> <https://urldefense.com/v3/__https://www.linkedin.com/in/abdallah-ismail15/__;!!D9dNQwwGXtA!X2cndMVKjcJZvViZc97OKfdFlf0AiMvrlvskjNibA8OZiU6zk9kumtPdj2BoU1yQizQqxAGApt0uQpw8Fe-tyDoRJQT3$>
>>
>>

-- 
*Abdallah Ibrahim Ismail*
GitHub Profile <https://github.com/Apolo151>
LinkedIn Profile <https://www.linkedin.com/in/abdallah-ismail15/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gsyc.urjc.es/pipermail/jde-developers/attachments/20250404/5ceafcd0/attachment.htm>


More information about the Jde-developers mailing list