Bug 785270 - test some bundle use-cases that aren't currently covered
Summary: test some bundle use-cases that aren't currently covered
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Provisioning
Version: 4.2
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-27 20:17 UTC by John Mazzitelli
Modified: 2012-02-07 19:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:25:44 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description John Mazzitelli 2012-01-27 20:17:45 UTC 
I think these use-cases currently work as advertised, but we don't have unit tests for these. I want to write unit tests to confirm this works and to have the tests for future.

TEST 1

1) deploy a bundle
2) in the destination directory, add a new file not part of the bundle (call it foo.txt)
3) deploy the same bundle from before - DO NOT make it a clean deployment

TEST 2

Same as TEST 1, only in step 3, DO make it a clean deployment (check the "clean" checkbox in the bundle deploy wizard)

The results should be the same. The foo.txt should be removed from the destination directory - it should not be left after the second deployment completes.
Comment 1 John Mazzitelli 2012-01-27 21:09:27 UTC 
git commit to master: 2dc60e4

org.rhq.core.util.updater.SimpleDeployerTest

testNoOriginalWithCurrentNoNew
testNoOriginalWithCurrentNoNew_Clean()
testNoOriginalWithCurrentNoNew_DryRun
testNoOriginalWithCurrentNoNew_DryRun_Clean

this is just code changes to unit tests. However, if QA wants to test this, try the test cases given in the description.
Comment 2 Mike Foley 2012-01-31 18:29:00 UTC 
regression tested Bundles: https://tcms.engineering.redhat.com/run/33098/   ---COMPLETE
Comment 3 Mike Foley 2012-02-07 19:25:44 UTC 
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE
Note You need to log in before you can comment on or make changes to this bug.