Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Fetching latest commit…

Cannot retrieve the latest commit at this time

..
Failed to load latest commit information.
step_definitions
support
README.md
global.feature
global_extra_data.feature
version.feature
vm.feature
vm_bios.feature
vm_cpu.feature
vm_extra_data.feature
vm_hw_virt.feature
vm_nat_engine.feature
vm_network_adapters.feature
vm_shared_folders.feature
vm_snapshots.feature
vm_storage_controllers.feature

README.md

VirtualBox Gem Feature Tests

Warning: These tests actually hit the real VirtualBox software!

The tests in this directory are not meant as a replacement for the unit tests in the test/ directory. Instead, these features are meant to test the actual integration of the virtualbox gem with an actual VirtualBox installation.

Whereas the unit tests try to test every branch of the code in a very prescribed, isolated environment, the feature tests do not test specific branches of code, but test behavior of the gem. The reasoning for both tests is that the unit tests test proper behavior within the library itself whereas these feature tests test proper behavior with the outside world.

Running Feature Tests

The easiest way to run these feature tests is via rake or the cucumber binary. rake shown below:

rake test:integration

Feature Coverage

The test coverage of the features are purposefully not trying to reach 100% branch coverage. They test the basic functionality (and as much as the functionality as possible) to verify the library is functional. If a bug is found, then a feature should be added to reproduce and verify the bug no longer exists, but I'm not concerned with getting 100% branch coverage right away.

For 100% branch coverage, see the unit tests, which do this.

Something went wrong with that request. Please try again.