From 90ac3951c894aa27e3d1cd214b41fb1dbe4e74a6 Mon Sep 17 00:00:00 2001 From: Jonathan Cave Date: Tue, 20 Aug 2019 16:22:16 +0100 Subject: gpio: import from p-p-snappy --- units/gpio/category.pxu | 9 +++++++++ units/gpio/jobs.pxu | 38 ++++++++++++++++++++++++++++++++++++++ units/gpio/test-plan.pxu | 40 ++++++++++++++++++++++++++++++++++++++++ 3 files changed, 87 insertions(+) create mode 100644 units/gpio/category.pxu create mode 100644 units/gpio/jobs.pxu create mode 100644 units/gpio/test-plan.pxu (limited to 'units/gpio') diff --git a/units/gpio/category.pxu b/units/gpio/category.pxu new file mode 100644 index 0000000..9433850 --- /dev/null +++ b/units/gpio/category.pxu @@ -0,0 +1,9 @@ +# Copyright 2015-2018 Canonical Ltd. +# All rights reserved. +# +# Written by: +# Maciej Kisielewski + +unit: category +id: gpio +_name: General Purpose I/O diff --git a/units/gpio/jobs.pxu b/units/gpio/jobs.pxu new file mode 100644 index 0000000..ec1e948 --- /dev/null +++ b/units/gpio/jobs.pxu @@ -0,0 +1,38 @@ +# This job currently has a template filter so that devices which do not yet +# have a pin definition file do not generate fails, when all devices have a +# definition this could be removed +unit: template +template-resource: com.canonical.certification::model_assertion +template-filter: model_assertion.model in ("pi2", "pi3", "ubuntu-core-18-pi2", "ubuntu-core-18-pi3") +template-unit: job +id: gpio/sysfs_loopback_pairs_{model} +_summary: Test GPIO lines exposed on headers can be controlled via sysfs +plugin: shell +user: root +category_id: gpio +command: + gpio_sysfs_loopback.py {model} +estimated_duration: 20.0 +flags: preserve-locale also-after-suspend + + +# Filtering this job by the same devices as above as uses the same pin +# definition file and uses the RPi python module +unit: template +template-resource: com.canonical.certification::model_assertion +template-filter: model_assertion.model in ("pi2", "pi3", "ubuntu-core-18-pi2", "ubuntu-core-18-pi3") +template-unit: job +id: gpio/gpiomem_loopback_pairs_{model} +_summary: Test GPIO lines exposed on headers can be controlled via /dev/gpiomem +plugin: shell +user: root +category_id: gpio +command: + gpio_gpiomem_loopback.py {model} +estimated_duration: 20.0 +flags: preserve-locale also-after-suspend +# If starting to test confinement then this connection will be requried: +#requires: +# {%- if __on_ubuntucore__ %} +# connections.slot == 'snapd:gpio-memory-control' and connections.plug == 'checkbox-plano:gpio-memory-control' +# {% endif -%} diff --git a/units/gpio/test-plan.pxu b/units/gpio/test-plan.pxu new file mode 100644 index 0000000..a32be08 --- /dev/null +++ b/units/gpio/test-plan.pxu @@ -0,0 +1,40 @@ +id: gpio-full +unit: test plan +_name: GPIO tests +_description: QA GPIO tests for Ubuntu Core devices +include: +nested_part: + gpio-manual + gpio-automated + +id: gpio-manual +unit: test plan +_name: Manual GPIO tests +_description: Manual GPIO tests for Ubuntu Core devices +include: + +id: after-suspend-gpio-manual +unit: test plan +_name: Manual GPIO tests (after suspend) +_description: Manual GPIO tests for Ubuntu Core devices (after suspend) +include: + +id: gpio-automated +unit: test plan +_name: Automated GPIO tests +_description: Automated GPIO tests for Ubuntu Core devices +bootstrap_include: + model_assertion +include: + gpio/sysfs_loopback_pairs_.* + gpio/gpiomem_loopback_pairs_.* + +id: after-suspend-gpio-automated +unit: test plan +_name: Automated GPIO tests (after suspend) +_description: Automated GPIO tests for Ubuntu Core devices (after suspend) +bootstrap_include: + model_assertion +include: + after-suspend-gpio/sysfs_loopback_pairs_.* + after-suspend-gpio/gpiomem_loopback_pairs_.* -- cgit v1.2.3