Description

Some time ago, I managed to convince ByteOtter to hack something that resembles isotovideo but in Rust, not because I believe that Perl is dead, but more because there are certain limitations in the perl code (how it was written), and its always hard to add new functionalities when they are about implementing a new backend, or fixing bugs (Along with people complaining that Perl is dead, and that they don't like it)

In reality, I wanted to see if this could be done, and ByteOtter proved that it could be, while doing an amazing job at hacking a vnc console, and helping me understand better what RuPerl needs to work.

I plan to keep working on this for the next few years, and while I don't aim for feature completion or replacing isotovideo tih isotest-ng (name in progress), I do plan to be able to use it on a daily basis, using specialized tooling with interfaces, instead of reimplementing everything in the backend

Todo

  • Add make targets for testability, e.g "spawn qemu and type"
  • Add image search matching algorithm
  • Add a Null test distribution provider
  • Add a Perl Test Distribution Provider
  • Fix unittests https://github.com/os-autoinst/isotest-ng/issues/5
  • Research OpenTofu how to add new hypervisors/baremetal to OpenTofu
  • Add an interface to openQA cli

Goals

  • Implement at least one of the above, prepare proposals for GSoC
  • Boot a system via it's BMC

Resources

See https://github.com/os-autoinst/isotest-ng

Looking for hackers with the skills:

rust openqa testing

This project is part of:

Hack Week 24

Activity

  • 12 months ago: szarate added keyword "rust" to this project.
  • 12 months ago: szarate added keyword "openqa" to this project.
  • 12 months ago: szarate added keyword "testing" to this project.
  • 12 months ago: szarate started this project.
  • 12 months ago: szarate originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    openQA log viewer by mpagot

    Description

    *** Warning: Are You at Risk for VOMIT? ***

    Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?

    You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).

    This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."

    Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.

    No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")

    This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.

    image

    Goals

    Work on the existing POC openqa-log-visualizer and change it to something usable

    Resources

    openqa-log-visualizer