From 4e423d5b7d9c2787ce8d9f979ea9093b5a2211ef Mon Sep 17 00:00:00 2001 From: Michael Hudson-Doyle Date: Thu, 18 Mar 2021 16:25:41 +1300 Subject: [PATCH] trivial DESIGN.md updates --- DESIGN.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/DESIGN.md b/DESIGN.md index 1c297793..8cdd9288 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -213,6 +213,7 @@ The simplest possible server controller would be something like this: import logging from subiquity.common.apidef import API +from subiquity.common.types import Type from subiquity.server.controller import SubiquityController log = logging.getLogger('subiquity.server.controllers.example') @@ -492,12 +493,17 @@ file". This yaml file provides data that controllers can use to drive the UI automatically. There are some answers files in the `examples/` directory that are run as a sort of integration test for the UI. -Tests (and lint checks) are run by travis using lxd. See `.travis.yml` and -`./scripts/test-in-lxd.sh` and so on. +Tests (and lint checks) are run by github actions using lxd. See +`.github/workflows/build.yaml` and `./scripts/test-in-lxd.sh` and so +on. -For "real" testing, you need to make a snap (`snapcraft snap`), mash it into an -existing ISO using `./scripts/inject-subiquity-snap.sh`, and boot the result in -a VM. +For "real" testing, you need to make a snap (`snapcraft snap`), mash +it into an existing ISO using `./scripts/inject-subiquity-snap.sh`, +and boot the result in a VM. There is an even hackier pair of scripts +(`./scripts/slimy-update-snap.sh` and +`./scripts/quick-test-this-branch.sh`) that can be useful for getting +small changes into an ISO much more quickly than making the snap from +scratch. There are integration tests that run daily at https://platform-qa-jenkins.ubuntu.com/view/server (unfortunately you need to