d8dfun/virtual-kubelet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity
Files
513cebe7b7cf590cd53c02ea8da1a20b58dd8f18
virtual-kubelet/vendor/github.com/vmware/vic/tests/test-cases/Group7-Regression/7-01-Regression.md
Loc Nguyen 513cebe7b7 VMware vSphere Integrated Containers provider (#206) 
* Add Virtual Kubelet provider for VIC

Initial virtual kubelet provider for VMware VIC.  This provider currently
handles creating and starting of a pod VM via the VIC portlayer and persona
server.  Image store handling via the VIC persona server.  This provider
currently requires the feature/wolfpack branch of VIC.

* Added pod stop and delete.  Also added node capacity.

Added the ability to stop and delete pod VMs via VIC.  Also retrieve
node capacity information from the VCH.

* Cleanup and readme file

Some file clean up and added a Readme.md markdown file for the VIC
provider.

* Cleaned up errors, added function comments, moved operation code

1. Cleaned up error handling.  Set standard for creating errors.
2. Added method prototype comments for all interface functions.
3. Moved PodCreator, PodStarter, PodStopper, and PodDeleter to a new folder.

* Add mocking code and unit tests for podcache, podcreator, and podstarter

Used the unit test framework used in VIC to handle assertions in the provider's
unit test.  Mocking code generated using OSS project mockery, which is compatible
with the testify assertion framework.

* Vendored packages for the VIC provider

Requires feature/wolfpack branch of VIC and a few specific commit sha of
projects used within VIC.

* Implementation of POD Stopper and Deleter unit tests (#4)

* Updated files for initial PR
2018-06-04 15:41:32 -07:00

1.2 KiB
Raw Blame History

Test 7-01 - Regression test

Purpose:

To verify general functionality of the product in a rapid, repeatable manner for regression testing of all commits

References:

1 - Docker Command Line Reference

Environment:

This test requires that a vSphere server is running and available

Test Steps:

  1. Deploy VIC appliance to the vSphere server
  2. Issue a docker pull busybox
  3. Issue a docker images, verify that busybox image shows up
  4. Issue a docker create busybox /bin/top
  5. Issue a docker start
  6. Issue a docker ps, verify that the container shows up as running
  7. Issue a docker stop
  8. Issue a docker ps, verify that the container is stopped
  9. Issue a docker rm
  10. Pull container log bundle from VICadmin and ensure that the container's vmware.log is present
  11. Issue a docker ps, verify that the container is removed
  12. Issue a docker rmi busybox
  13. Issue a docker images, verify that busybox image is gone
  14. Remove the VIC appliance with vic-machine delete command, verify that the appliance was removed

Expected Outcome:

VIC appliance should respond without error to each of the commands

Possible Problems:

None