Project Description
Inspired by one of the proposals for GSoC and given that I'm usually working on maintenance updates for SUSE Manager - Uyuni I decided to translate it to Italian. :)
Goal for this Hackweek
Given the amount of strings to be translated I'll focus on the product, leaving the user guides for the next future.
Resources
Some more details are available also here:
Looking for hackers with the skills:
This project is part of:
Hack Week 20
Activity
Comments
-
over 4 years ago by deneb_alpha | Reply
There are already some translation provided but several are also outdated.
For hackweek I'm planning to start with the untranslated strings and, when ended, to review the old existing strings.
-
over 4 years ago by deneb_alpha | Reply
WebUI
- Java -> 349 strings to be translated
-
over 4 years ago by deneb_alpha | Reply
Looks like we still have some references to SUSE Studio: like here
-
-
-
-
over 4 years ago by deneb_alpha | Reply
something went wrong... :(
Note to self, when tired, have a break ;)
-
over 4 years ago by deneb_alpha | Reply
translations still ongoing...
This day two seems to be harder. The translations units I'm handling today are not easy to be translated to Italian in a meaningful way. Some strings are also extremely short or with a lot of code tag. SUMA folks gave me access to a demo instance for having the strings context a little bit easier to get. Moving forward checking carefully for avoiding to break tags and other parts that should not be translated
-
-
over 4 years ago by deneb_alpha | Reply
here we go... :)
This component https://l10n.opensuse.org/projects/uyuni/java/it/ is done. waiting to see it merged.
Moving to the next.
-
over 4 years ago by deneb_alpha | Reply
also the component https://l10n.opensuse.org/projects/uyuni/java-database/it/ is done. :)
moving to the next!
-
over 4 years ago by deneb_alpha | Reply
good progress for today and in parallel I have also done some reviews of existing translations trying to use the same working in similar context.
The route is still long but the trip is exciting! :)
-
over 4 years ago by deneb_alpha | Reply
I'll take some notes here on things that should be checked and refined for a better and meaningful translation
-
over 4 years ago by deneb_alpha | Reply
- Working on a common glossary
- Errata -> better to use patch. it's used in Italian
-
-
over 4 years ago by deneb_alpha | Reply
Collecting here via replies the different issues I reported.
-
Similar Projects
Flaky Tests AI Finder for Uyuni and MLM Test Suites by oscar-barrios
Description
Our current Grafana dashboards provide a great overview of test suite health, including a panel for "Top failed tests." However, identifying which of these failures are due to legitimate bugs versus intermittent "flaky tests" is a manual, time-consuming process. These flaky tests erode trust in our test suites and slow down development.
This project aims to build a simple but powerful Python script that automates flaky test detection. The script will directly query our Prometheus instance for the historical data of each failed test, using the jenkins_build_test_case_failure_age metric. It will then format this data and send it to the Gemini API with a carefully crafted prompt, asking it to identify which tests show a flaky pattern.
The final output will be a clean JSON list of the most probable flaky tests, which can then be used to populate a new "Top Flaky Tests" panel in our existing Grafana test suite dashboard.
Goals
By the end of Hack Week, we aim to have a single, working Python script that:
- Connects to Prometheus and executes a query to fetch detailed test failure history.
- Processes the raw data into a format suitable for the Gemini API.
- Successfully calls the Gemini API with the data and a clear prompt.
- Parses the AI's response to extract a simple list of flaky tests.
- Saves the list to a JSON file that can be displayed in Grafana.
- New panel in our Dashboard listing the Flaky tests
Resources
- Jenkins Prometheus Exporter: https://github.com/uyuni-project/jenkins-exporter/
- Data Source: Our internal Prometheus server.
- Key Metric:
jenkins_build_test_case_failure_age{jobname, buildid, suite, case, status, failedsince}. - Existing Query for Reference:
count by (suite) (max_over_time(jenkins_build_test_case_failure_age{status=~"FAILED|REGRESSION", jobname="$jobname"}[$__range])). - AI Model: The Google Gemini API.
- Example about how to interact with Gemini API: https://github.com/srbarrios/FailTale/
- Visualization: Our internal Grafana Dashboard.
- Internal IaC: https://gitlab.suse.de/galaxy/infrastructure/-/tree/master/srv/salt/monitoring
Move Uyuni Test Framework from Selenium to Playwright + AI by oscar-barrios
Description
This project aims to migrate the existing Uyuni Test Framework from Selenium to Playwright. The move will improve the stability, speed, and maintainability of our end-to-end tests by leveraging Playwright's modern features. We'll be rewriting the current Selenium code in Ruby to Playwright code in TypeScript, which includes updating the test framework runner, step definitions, and configurations. This is also necessary because we're moving from Cucumber Ruby to CucumberJS.
If you're still curious about the AI in the title, it was just a way to grab your attention. Thanks for your understanding.
Goals
- Migrate Core tests including Onboarding of clients
- Improve test reliabillity: Measure and confirm a significant reduction of flakynes.
- Implement a robust framework: Establish a well-structured and reusable Playwright test framework using the CucumberJS
Resources
- Existing Uyuni Test Framework (Cucumber Ruby + Capybara + Selenium)
- My Template for CucumberJS + Playwright in TypeScript
- Started Hackweek Project