Occasionally, new versions of openQA break things. How do you stop that? MORE TESTING!

Testing openQA by using openQA to ensure the new versions don't break should be a good example of how openQA can test everything and anything, even itself.

Not only should it be a fun exercise to have the current version of openQA testing the next version of openQA before it's deployed, but it's a chance to stretch the nested virtualisation capabilities of openQA and have it test individual packages/repositories from OBS instead of ISO based 'products' or HDD based images.

Help hack openQA so it can test itself before we deploy new versions, and stop any quirks in that new release making my life like this gif What's going on?

Looking for mad skills in:

Nothing? Add some keywords!

This project is part of:

Hack Week 12

Activity

  • over 1 year ago: guohouzuo disliked Test openQA in openQA with openQA using openQA for openQA
  • over 3 years ago: xgonzo liked Test openQA in openQA with openQA using openQA for openQA
  • over 3 years ago: ganglia liked Test openQA in openQA with openQA using openQA for openQA
  • over 3 years ago: bchou liked Test openQA in openQA with openQA using openQA for openQA
  • over 3 years ago: pluskalm liked Test openQA in openQA with openQA using openQA for openQA
  • Show History

    Comments

    Be the first to comment!

    Similar Projects

    This project is one of its kind!