From Fedora Project Wiki

Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
 
|description=This test is to make sure that the user is able to run docker-storage-setup' successfully after installing Docker.
 
|description=This test is to make sure that the user is able to run docker-storage-setup' successfully after installing Docker.
|setup=Test this on Atomic image.
+
|setup=Test this on Atomic image and Base image.
 
|actions=
 
|actions=
 
Be as specific as required for the target audience.  
 
Be as specific as required for the target audience.  
# ssh into an Atomic image.
+
# ssh into an Atomic/Base instance.
 
# Next we will check if we can run docker-storage-setup.
 
# Next we will check if we can run docker-storage-setup.
 
# Finally we will list information about all available block devices. We will read sysfs filesystem and udev db to gather information.
 
# Finally we will list information about all available block devices. We will read sysfs filesystem and udev db to gather information.
Line 14: Line 14:
 
|results=
 
|results=
 
The following must be true to consider this a successful test run.
 
The following must be true to consider this a successful test run.
# Step #1 You should be able to login in to an atomic image.
+
# Step #1 You should be able to login in to an instance.
 
# Step #2 will give you output like this:
 
# Step #2 will give you output like this:
  

Revision as of 10:03, 5 May 2016

Description

This test is to make sure that the user is able to run docker-storage-setup' successfully after installing Docker.

Setup

Test this on Atomic image and Base image.

How to test

Be as specific as required for the target audience.

  1. ssh into an Atomic/Base instance.
  2. Next we will check if we can run docker-storage-setup.
  3. Finally we will list information about all available block devices. We will read sysfs filesystem and udev db to gather information.

We will execute these commands:

 $ journalctl -o cat --unit docker-storage-setup.service
 $ lsblk

Expected Results

The following must be true to consider this a successful test run.

  1. Step #1 You should be able to login in to an instance.
  2. Step #2 will give you output like this:
 $ CHANGED: partition=2 start=411648 old: size=12171264 end=12582912 new: size=41531232,end=41942880
 Physical volume "/dev/vda2" changed
 1 physical volume(s) resized / 0 physical volume(s) not resized
 Size of logical volume atomicos/root changed from 1.95 GiB (500 extents) to 4.00 GiB (1024 extents).
 Logical volume root successfully resized
 Rounding up size to full physical extent 24.00 MiB
 Logical volume "docker-meta" created
 Logical volume "docker-data" created

3. Step #3 will give you output like this:

 $ NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
 vda                       252:0    0   20G  0 disk 
 ├─vda1                    252:1    0  200M  0 part /boot
 └─vda2                    252:2    0 19.8G  0 part 
   ├─atomicos-root         253:0    0    4G  0 lvm  /sysroot
   ├─atomicos-docker--meta 253:1    0   24M  0 lvm  
   └─atomicos-docker--data 253:2    0   10G  0 lvm

Optional

Optionally provide hints for exploratory testing.