Project Description

Our current workflow for contributing to compliance as code requires manual testing. Automated testing either through the upstream CI or openQA would lower development time.

Goal for this Hackweek

  • Working prototype for OpenQA testing (hard, but openQA is awesome) OR
  • Testing for SLES on the upstream CI (probably easier, but needs cooperation from upstream)

Resources

Compliance as Code - Upstream

Documentation for openQA

Looking for hackers with the skills:

openqa complianceascode github-ci

This project is part of:

Hack Week 22

Activity

  • about 2 months ago: c-hagenest left this project.
  • about 2 months ago: okurz liked this project.
  • about 2 months ago: abergmann liked this project.
  • 2 months ago: idefx disliked this project.
  • 2 months ago: idefx liked this project.
  • 2 months ago: robert.richardson liked this project.
  • 2 months ago: tschmitz liked this project.
  • 2 months ago: cdywan liked this project.
  • 2 months ago: c-hagenest started this project.
  • 2 months ago: c-hagenest added keyword "complianceascode" to this project.
  • 2 months ago: c-hagenest added keyword "github-ci" to this project.
  • 2 months ago: c-hagenest added keyword "openqa" to this project.
  • 2 months ago: c-hagenest originated this project.

  • Comments

    Be the first to comment!

    Similar Projects

    QJobViewer by apappas

    [comment]: # (Please use the project descriptio...


    OpenQA test list views improvement by mdati

    Project Description

    Create views of **Ope...


    Implement text based OCR in openQA by clanig

    Project Description

    Currently openQA requir...


    Learn PostgreSQL advanced features by okurz

    Motivation

    The PostgreSQL database implement...


    Improve OpenSCAP support in Uyuni by admehmood

    [comment]: # (Please use the project descriptio...