The salt-toaster (https://github.com/openSUSE/salt-toaster) is a tool created and developed by SUSE employees that we've been using for testing Salt since few years ago.

This tool uses pytest in combination with Docker containers to allow testing the multiple versions of the Salt codebase and as well as Salt packages across multiple distributions.

The tests are separated in 3 groups:

  • Upstream integration tests
  • Upstream unit tests
  • SUSE custom integration tests

Currently, the "salt-toaster" is in a shape that only allows to run the tests inside SUSE (because it depends on our internal Docker registry).

The main goals of this HW project are:

  • Allow running tests without necessary having access to our internal Docker registry.
  • Make testing Salt really easy for newcomers.

Some of tasks needed in order to reach those goals are:

  • Define and push some base toaster images to Docker hub (based on openSUSE and probably CentOS)
  • Improve the documentation. Paying special attention on users outside SUSE.
  • Screencast showing how to start running tests.

There is also a need from SaltStack upstream to provide an easy way for people to run the tests, so this is an opportunity to make the salt-toaster as the default tool for testing Salt also for contributors and people outside SUSE.

Looking for hackers with the skills:

testing salt community opensuse docker documentation python

This project is part of:

Hack Week 18

Activity

  • over 6 years ago: joachimwerner liked this project.
  • over 6 years ago: Pharaoh_Atem liked this project.
  • over 6 years ago: PSuarezHernandez added keyword "python" to this project.
  • over 6 years ago: PSuarezHernandez liked this project.
  • over 6 years ago: PSuarezHernandez added keyword "documentation" to this project.
  • over 6 years ago: PSuarezHernandez added keyword "testing" to this project.
  • over 6 years ago: PSuarezHernandez added keyword "salt" to this project.
  • over 6 years ago: PSuarezHernandez added keyword "community" to this project.
  • over 6 years ago: PSuarezHernandez added keyword "opensuse" to this project.
  • over 6 years ago: PSuarezHernandez added keyword "docker" to this project.
  • over 6 years ago: PSuarezHernandez started this project.
  • over 6 years ago: PSuarezHernandez originated this project.

  • Comments

    • mdinca
      over 6 years ago by mdinca | Reply

      It was possible at some time to run the tests using leap: https://github.com/openSUSE/salt-toaster/commit/400f266141745e9cf943f741ce78960378da2bbf#diff-354f30a63fb0907d4ad57269548329e3

    • PSuarezHernandez
      over 6 years ago by PSuarezHernandez | Reply

      Results for this HW project! https://github.com/openSUSE/salt-toaster/pull/74

    Similar Projects

    Create openSUSE images for Arm/RISC-V boards by avicenzi

    Project Description

    Create openSUSE images (or test generic EFI images) for Arm and/or RISC-V boards that are not yet supported.

    Goal for this Hackweek

    Create bootable images of Tumbleweed for SBCs that currently have no images available or are untested.

    Consider generic EFI images where possible, as some boards can hold a bootloader.

    Document in the openSUSE Wiki how to flash and use the image for a given board.

    Boards that I have around and there are no images:

    • Rock 3B
    • Nano PC T3 Plus
    • Lichee RV D1
    • StartFive VisionFive (has some image needs testing)

    Hack Week 22

    Hack Week 21

    Resources


    Advent of Code: The Diaries by amanzini

    Description

    It was the Night Before Compile Time ...

    Hackweek 25 (December 1-5) perfectly coincides with the first five days of Advent of Code 2025. This project will leverage this overlap to participate in the event in real-time.

    To add a layer of challenge and exploration (in the true spirit of Hackweek), the puzzles will be solved using a non-mainstream, modern language like D, Crystal, Gleam or Zig.

    The primary project intent is not just simply to solve the puzzles, but to exercise result sharing and documentation. I'd create a public-facing repository documenting the process. This involves treating each day's puzzle as a mini-project: solving it, then documenting the solution with detailed write-ups, analysis of the language's performance and ergonomics, and visualizations.

                                   |
                                 \ ' /
                               -- (*) --
                                  >*<
                                 >0<@<
                                >>>@<<*
                               >@>*<0<<<
                              >*>>@<<<@<<
                             >@>>0<<<*<<@<
                            >*>>0<<@<<<@<<<
                           >@>>*<<@<>*<<0<*<
             \*/          >0>>*<<@<>0><<*<@<<
         ___\\U//___     >*>>@><0<<*>>@><*<0<<
         |\\ | | \\|    >@>>0<*<0>>@<<0<<<*<@<<
         | \\| | _(UU)_ >((*))_>0><*<0><@<<<0<*<
         |\ \| || / //||.*.*.*.|>>@<<*<<@>><0<<<
         |\\_|_|&&_// ||*.*.*.*|_\\db//_
         """"|'.'.'.|~~|.*.*.*|     ____|_
             |'.'.'.|   ^^^^^^|____|>>>>>>|
             ~~~~~~~~         '""""`------'
    ------------------------------------------------
    This ASCII pic can be found at
    https://asciiart.website/art/1831
    
    

    Goals

    Code, Docs, and Memes: An AoC Story

    • Have fun!

    • Involve more people, play together

    • Solve Days 1-5: Successfully solve both parts of the Advent of Code 2025 puzzles for Days 1-5 using the chosen non-mainstream language.

    • Daily Documentation & Language Review: Publish a detailed write-up for each day. This documentation will include the solution analysis, the chosen algorithm, and specific commentary on the language's ergonomics, performance, and standard library for the given task.