| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Since lets can't be used in before :all any more.
|
|
The `retrieve` method was calling `create` and `destroy` on every run
with `force => true`. Retrieve should not be making any changes to the
system, so removed that code, and updated `working_copy_exists` to make
sure that the directory not only contains a `.git` directory, but also
if `source` is specified it also matches `#{path}/.git/config` so that
it will overwrite a git repo with a different source.
Updated tests to not check for the old broken behavior. Added a regression test.
|
|
This conversion is done by Transpec 2.3.7 with the following command:
transpec
* 22 conversions
from: it { should ... }
to: it { is_expected.to ... }
* 19 conversions
from: obj.should
to: expect(obj).to
* 15 conversions
from: == expected
to: eq(expected)
* 5 conversions
from: it { should_not ... }
to: it { is_expected.not_to ... }
* 2 conversions
from: its(:attr) { }
to: describe '#attr' do subject { super().attr }; it { } end
* 2 conversions
from: obj.should_not
to: expect(obj).not_to
* 2 conversions
from: proc { }.should
to: expect { }.to
* 1 conversion
from: be_false
to: be_falsey
* 1 conversion
from: be_true
to: be_truthy
For more details: https://github.com/yujinakayama/transpec#supported-conversions
|
|
Previously we were using `puppet_module_install()`. Which was ported from
Beaker-RSpec. Unfortunately for our heros that method has been refactored
since this was ran last. The method `puppet_module_install()` in Beaker
installs from the public forge, while the previous behavior, installing via
scp from the current directory, has moved to the method `copy_module_to`.
This updates the helper for the beaker tests to use the updated method.
|
|
|
|
Previously vcsrepo detached HEAD on checkout which caused further branch
revisions to fail. This corrects the behavior, and works on git 1.7,
1.8, 1.9, and 2.0
|
|
|
|
|
|
Update noop to work
|
|
|
|
|
|
Previously we were creating the module dir on foss installs, but not on PE.
PE agents do not have a module dir deployed as part of the base PE install,
so to test on PE agents we need to create the module dir. `mkdir -p` is
idempotent, so we use it as a cudgle here. We also update the beaker_helper
and spec_helper_acceptance to contain the same installation steps for test
dependencies, warnings, and installation methods.
|
|
A matching group is not added for a user when added on SLES 11.
This commit adds a group to the setup manifests in order to
ensure that the proper group is added to the system during the
test preparation.
|
|
This test is pending as git cannot handle the overflow correctly, though
vcsrepo handles it fine.
|
|
Add conditional to install `git-core` if the platform under test
is ubuntu-10. The `git` package is not available for this platform.
|
|
The git-daemon is not a valid package on debian based systems.
Update tests to not try installing git-daemon on debian systems.
|
|
The manifest is set to clone at a depth of 1, but checks for a shallow
depth of 2. It should either checkout a depth of 2, or only check for a
depth of 1.
This commit makes it check for a depth of 1
|
|
|
|
|
|
|
|
|
|
|
|
In ubuntu 14.04 git 1.9.1 is the default version, and 1.9+ fatally fail
if the user.email and user.name are not set (previously it would just
warn). This commit sets those up so the tests will actually run.
|
|
When the revision attribute is defined in conjunction with the bare
attribute when using the git provider, the repo should fail to be
written to disk.
See: FM-1361
|
|
- Add install.rb for pre-suite
- Add catches for failures/changes to manifest application
- Correct root ssh key copying
- Add sleeps for killing processes releasing ports
- Fix FM-1361
|
|
The protocol tests are more closely aligned with the rest of the beaker test
suite. The beaker tests have received more vetting, so the setup and teardown
process should be less prone to failure on repeated execution.
|
|
Add test for ensure latest with branch specified
|
|
Add beaker tests to complete test plan
|
|
These tests assert the vagrant user and group. When testing on non-vagrant systems these tests
will fail. Ensure that the user/group are present in order to allow the tests to pass on
other systems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
