Skip to content
This repository has been archived by the owner on Aug 30, 2024. It is now read-only.

Integration Tests #49

Open
nkubala opened this issue Nov 1, 2016 · 0 comments
Open

Integration Tests #49

nkubala opened this issue Nov 1, 2016 · 0 comments

Comments

@nkubala
Copy link
Contributor

nkubala commented Nov 1, 2016

cc @dlorenc @sharifelgamal

unsure if these are applicable to Debian, but creating this bug to track here. my original comment:

I'm imagining something like installing and running a list of software packages, or maybe even a language runtime, and just checking certain simple interactions between the software and Debian itself (syscalls, etc). Maybe these are more integration tests of the underlying software and not Debian.

just sparking a little discussion on whether we think these apply to Debian at all. can close if we decide they're not going to happen.
dlorenc pushed a commit that referenced this issue Nov 21, 2017
@nkubala
support for setup/teardown commands in cmd tests (#49)
435569b 
* add ability to substitute env vars into command output/error

* add support for setup/teardown commands. remove flags field in favor of just providing command string.

* fix file/directory existence logging

* gofmt

* change build script to take entire image path instead of just tag

* add back flags field

* remove env vars field. hardcode replacing PWD in output/error regexes

* remove flags field. change command field to a list of strings, containing flags

* unify running setup/teardown/normal commands. restructure methods

* update documentation

* update tag check test config

* remove duplicate code. fix readme

* remove envvar substitution function and move PWD hack to regex compiler

* remove pwd hack
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nkubala