File: task.yaml

package info (click to toggle)
snapd 2.71-3
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 79,536 kB
  • sloc: ansic: 16,114; sh: 16,105; python: 9,941; makefile: 1,890; exp: 190; awk: 40; xml: 22
file content (27 lines) | stat: -rw-r--r-- 1,229 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
summary: simple completion

details: |
  Snapd contains a special system for tab-completion of snap applications, where
  the bulk of the completion logic runs under confinement, and communicates with
  a trusted, unconfined helper provided by snapd.

  Like all the other completion tests, this test relies on a set of files
  $variant.{complete,sh,vars} where foo $variant is one of the many variants of
  the tests/complete suite: plain, plain_plusdirs, funky, files, hosts,
  hosts_n_dirs, func, funkyfunc, funcarg. In each case the .vars file adds
  environment variables needed by the test, the .sh script is executed during
  test setup and the .complete script replaces the bash completer in the
  test-snapd-complexion snap.

  Like all the other completion tests this test is mostly implemented with
  expect(1) to interact with bash, send and receive snippets of text.

  This test relies bypasses the complete.sh/etelpmoc.sh pair of scripts and does
  not communicate across the barrier created by the snap execution sandbox.

execute: |
  d="$PWD"
  #shellcheck disable=SC1090
  source "${SPREAD_PATH}/${SPREAD_SUITE}/${SPREAD_VARIANT}.vars"
  export _OUT0 _OUT1 _OUT2 _KEY1 _KEY2 _COMP
  expect -d -f "$d"/task.exp