Use different keyring in system tests.

This commit is contained in:
Andrey Smirnov
2014-02-12 21:25:55 +04:00
parent 5bf370e18a
commit fb2e1adb5c
8 changed files with 38 additions and 19 deletions
+3 -3
View File
@@ -51,7 +51,7 @@ class DropSnapshot4Test(BaseTest):
fixturePool = True
fixtureCmds = [
"aptly snapshot create snap1 from mirror gnuplot-maverick",
"aptly publish snapshot snap1"
"aptly publish snapshot -keyring=${files}/aptly.pub -secret-keyring=${files}/aptly.sec snap1"
]
runCmd = "aptly snapshot drop snap1"
expectedCode = 1
@@ -65,7 +65,7 @@ class DropSnapshot5Test(BaseTest):
fixturePool = True
fixtureCmds = [
"aptly snapshot create snap1 from mirror gnuplot-maverick",
"aptly publish snapshot snap1"
"aptly publish snapshot -keyring=${files}/aptly.pub -secret-keyring=${files}/aptly.sec snap1"
]
runCmd = "aptly snapshot drop --force snap1"
expectedCode = 1
@@ -88,7 +88,7 @@ class DropSnapshot7Test(BaseTest):
fixturePool = True
fixtureCmds = [
"aptly snapshot create snap1 from mirror gnuplot-maverick",
"aptly publish snapshot snap1",
"aptly publish snapshot -keyring=${files}/aptly.pub -secret-keyring=${files}/aptly.sec snap1",
"aptly publish drop maverick",
]
runCmd = "aptly snapshot drop snap1"