# Introduction - Interested in system test Improvement project

**URL:** <https://precice.discourse.group/t/introduction-interested-in-system-test-improvement-project/2812>\
**Category:** Google Summer of Code\
**Tags:** gsoc-system-tests, gsoc-period-reachout\
**Created:** [March 9, 2026, 8:33am UTC](https://precice.discourse.group/t/introduction-interested-in-system-test-improvement-project/2812 "2026-03-09T08:33:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TanujSharma](https://avatars.discourse-cdn.com/v4/letter/t/cc9497/32.png) [@TanujSharma](https://precice.discourse.group/u/TanujSharma)\
**Post date:** [March 9, 2026, 8:33am UTC](https://precice.discourse.group/t/introduction-interested-in-system-test-improvement-project/2812/1 "2026-03-09T08:33:29Z")

</div>

Hello everyone,

My name is Tanuj Sharma. I am interested in contributing to preCICE under the Google Summer of Code program.

Currently, I am looking into the **System Test Improvement** project and planning to work on the entry task of running the system tests locally and adding a tutorial to the tests.

I have experience with **Python, Docker, and GitHub Actions** , and I am interested in applying these skills while learning more about the testing infrastructure in preCICE.

I would appreciate any guidance or suggestions on getting started with the system tests and contributing effectively.

Thank you!

---

<div class="post-metadata">

**Author:** ![TanujSharma](https://avatars.discourse-cdn.com/v4/letter/t/cc9497/32.png) [@TanujSharma](https://precice.discourse.group/u/TanujSharma)\
**Post date:** [March 28, 2026, 9:12am UTC](https://precice.discourse.group/t/introduction-interested-in-system-test-improvement-project/2812/2 "2026-03-28T09:12:42Z")

</div>

Update: I have been actively working on the entry test. So far I have:

- Fixed a Dockerfile syntax bug in Dockerfile.openfoam-adapter  
(inline comment on SHELL instruction causing parse errors)
- Resolved the python-is-python3 compatibility issue for Ubuntu 20.04
- Upgraded CMake to 3.22.1+ using the Kitware APT repository
- Explored the GitHub Actions workflow structure in the tutorials repo

I have also prepared my GSoC proposal. Would love any feedback  
from the mentors!

GitHub: [github.com/Tanuj-Sharma-12](http://github.com/Tanuj-Sharma-12)

---

<div class="post-metadata">

**Author:** ![TanujSharma](https://avatars.discourse-cdn.com/v4/letter/t/cc9497/32.png) [@TanujSharma](https://precice.discourse.group/u/TanujSharma)\
**Post date:** [March 28, 2026, 2:48pm UTC](https://precice.discourse.group/t/introduction-interested-in-system-test-improvement-project/2812/3 "2026-03-28T14:48:18Z")

</div>

Update on my entry test progress:

I have successfully added the oscillator tutorial to the  
preCICE system tests:

- Created metadata.yaml for the oscillator tutorial  
(with mass-left-python and mass-right-python cases)
- Added oscillator\_test suite to tools/tests/tests.yaml
- Verified using print\_metadata.py and print\_test\_suites.py  
— the tutorial is correctly recognized by the system

I also worked extensively on the older systemtests repository,  
where I fixed several issues:

- Fixed a Dockerfile syntax bug in Dockerfile.openfoam-adapter  
(inline comment on SHELL instruction causing parse errors)
- Resolved the python-is-python3 compatibility issue for Ubuntu 20.04
- Upgraded CMake to 3.22.1+ using the Kitware APT repository

My work on the tutorials fork is available here:

> **[GitHub - TanujSharma-12/tutorials at add-oscillator-system-test](https://github.com/TanujSharma-12/tutorials/tree/add-oscillator-system-test)**
>
> Various tutorial cases for the coupling library preCICE with real solvers. These files are meant to be rendered on precice.org, so don't look at the README files here. - TanujSharma-12/tutorials

I tried opening a PR to precice/tutorials but the repository  
requires collaborator access. I would love any feedback from  
@fsimonis and @Makis on my approach!

---

<div class="post-metadata">

**Author:** ![TanujSharma](https://avatars.discourse-cdn.com/v4/letter/t/cc9497/32.png) [@TanujSharma](https://precice.discourse.group/u/TanujSharma)\
**Post date:** [March 31, 2026, 9:45am UTC](https://precice.discourse.group/t/introduction-interested-in-system-test-improvement-project/2812/4 "2026-03-31T09:45:42Z")

</div>

Hi @Makis,

I have successfully submitted my GSoC 2026 proposal for the System Tests Improvements.  
Looking forward to your feedback!

Tanuj Sharma

---

<div class="post-metadata">

**Author:** ![TanujSharma](https://avatars.discourse-cdn.com/v4/letter/t/cc9497/32.png) [@TanujSharma](https://precice.discourse.group/u/TanujSharma)\
**Post date:** [April 6, 2026, 9:59am UTC](https://precice.discourse.group/t/introduction-interested-in-system-test-improvement-project/2812/5 "2026-04-06T09:59:54Z")

</div>

Hi @Makis,

While reading the preCICE system tests documentation at [preCICE system tests | preCICE - The Coupling Library](http://precice.org/dev-docs-system-tests) , I noticed this comment:

“The Docker Compose services consider GitHub Actions Cache when building the services, although the cache is currently only updated, but not hit.”

This means the cache is being saved but never actually used, causing every build to start from scratch. As part of my proposed work on faster builds, I would like to investigate and fix this. Could you help me understand why the cache is not being hit currently? Is there a known reason for this,  
or was it never fully implemented?

Thank you!
