Skip to content

Commit b5db154

Browse files
committed
Add integration test to challenge the resolver to find an old corrrect revision
This is basically testing what is manually reported by @juanmanuel-tirado in the following review: #830 (comment)
1 parent 4308378 commit b5db154

1 file changed

Lines changed: 9 additions & 2 deletions

File tree

tests/integration/test_model.py

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,12 +97,19 @@ async def test_deploy_bundle_local_resource_relative_path(event_loop):
9797
async def test_deploy_by_revision(event_loop):
9898
async with base.CleanModel() as model:
9999
app = await model.deploy('juju-qa-test',
100-
application_name='test',
100+
application_name='test1',
101101
channel='2.0/stable',
102-
revision=22,)
102+
revision=22)
103103

104104
assert url.URL.parse(app.charm_url).revision == 22
105105

106+
app = await model.deploy('juju-qa-test',
107+
application_name='test2',
108+
channel='latest/edge',
109+
revision=19)
110+
111+
assert url.URL.parse(app.charm_url).revision == 19
112+
106113

107114
@base.bootstrapped
108115
@pytest.mark.asyncio

0 commit comments

Comments
 (0)