openSUSE Leap 42.3 goes for a rolling release model with automated openQA tests. That covers only so much though. We need manual testing too. In previous releases a google document spread sheet was used to coordinate and track the efforts.That's probably not the best method anymore.

Come up with ideas and a prototype of how manual testing could be guided, tracked, visualized for a rolling development distribution with volunteers testing.

See also https://progress.opensuse.org/issues/13762

Looking for hackers with the skills:

opensuse qa webapps

This project is part of:

Hack Week 16 Hack Week 19

Activity

  • over 5 years ago: szarate started this project.
  • over 5 years ago: mlin7442 liked this project.
  • over 5 years ago: deneb_alpha liked this project.
  • almost 8 years ago: szarate liked this project.
  • almost 8 years ago: ldevulder liked this project.
  • almost 8 years ago: mstrigl liked this project.
  • over 8 years ago: okurz liked this project.
  • over 8 years ago: hennevogel liked this project.
  • over 8 years ago: lnussel added keyword "opensuse" to this project.
  • over 8 years ago: lnussel added keyword "qa" to this project.
  • over 8 years ago: lnussel added keyword "webapps" to this project.
  • over 8 years ago: lnussel originated this project.

  • Comments

    • szarate
      over 5 years ago by szarate | Reply

      Maybe investigate https://kiwitcms.org/

    • szarate
      over 5 years ago by szarate | Reply

      So I did set up a "sample" thing, it's running at http://phobos.suse.de:8000/ will play a bit more later on. Initially, I think It might serve the needs with few adaptations (if needed).

      Users can register, and they will be activated instantly (Regardless of the message)

    • szarate
      over 5 years ago by szarate | Reply

      There are two runs recorded: http://phobos.suse.de:8000/runs/1/

    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