From Fedora Project Wiki

(updated after comments on test case content)
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{admon/note|Draft Test Case|This test case is still an early draft, suggestions and/or improvements are welcome}}
{{QA/Test_Case
{{QA/Test_Case
|description=
|description=
A simple validation test case for Fedora images on Amazon EC2, the specific actions used after spawning the instance are not important as anything beyond successfully spawning an instance from a Fedora AMI is covered by other test cases not specific to EC2.
A simple validation test case for Fedora images on Amazon EC2, the specific actions used after spawning the instance are not important as anything beyond successfully spawning an instance from a Fedora AMI is covered by other test cases not specific to EC2.


More documentation on interacting with EC2 is available in [http://docs.amazonwebservices.com/AWSEC2/latest/GettingStartedGuide/ Amazon's AWS Getting Started Guide].
More documentation on interacting with EC2 is available in [http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Cloud_Guide/ch02.html#sec-cloud-guide-AmazonEC2 the Fedora Cloud Guide].
|setup=
|setup=
# Get an AWS account (the approval process can take hours)
# Get an AWS account (the approval process can take hours)
Line 11: Line 9:
# Log in to the AWS Management Console
# Log in to the AWS Management Console
|actions=
|actions=
# Obtain the AMI id of the newest Fedora image from [[Cloud_images | the list of Fedora AMI ids]].
# Obtain the AMI id of the newest Fedora image from [http://cloud.fedoraproject.org/ http://cloud.fedoraproject.org/].
# Search for and select the desired AMI on the IMAGES/AMIs section of the EC2 console
# Search for and select the desired AMI on the IMAGES/AMIs section of the EC2 console
# Launch an instance with the AMI under test
# Launch an instance with the AMI under test
# Log in to the launched AMI using the ec2-user user and the SSH keypair selected during instance launch
# Log in to the launched AMI using the <code>fedora</code> user and the SSH keypair selected during instance launch
# Using a workflow you are familiar with, install packages and verify basic functionality
# Using a workflow you are familiar with, install packages and verify basic functionality
|results=
|results=
# The AMI launches successfully
# The AMI launches successfully
# You can login to the instance over SSH as ec2-user and you have sudo access
# You can login to the instance over SSH as <code>fedora</code> and you have sudo access
# You can install packages from the yum repositories
# You can install packages from the yum repositories (For example, <tt>sudo yum -y install httpd</tt>.)
# The instance doesn't crash or show any errors that aren't present in a bare-metal system
# The instance doesn't crash or show any errors that aren't present in a bare-metal system
}}
}}

Latest revision as of 18:06, 31 July 2013

Description

A simple validation test case for Fedora images on Amazon EC2, the specific actions used after spawning the instance are not important as anything beyond successfully spawning an instance from a Fedora AMI is covered by other test cases not specific to EC2.

More documentation on interacting with EC2 is available in the Fedora Cloud Guide.

Setup

  1. Get an AWS account (the approval process can take hours)
  2. Make sure that your security group allows for SSH (default tcp port 22)
  3. Log in to the AWS Management Console

How to test

  1. Obtain the AMI id of the newest Fedora image from http://cloud.fedoraproject.org/.
  2. Search for and select the desired AMI on the IMAGES/AMIs section of the EC2 console
  3. Launch an instance with the AMI under test
  4. Log in to the launched AMI using the fedora user and the SSH keypair selected during instance launch
  5. Using a workflow you are familiar with, install packages and verify basic functionality

Expected Results

  1. The AMI launches successfully
  2. You can login to the instance over SSH as fedora and you have sudo access
  3. You can install packages from the yum repositories (For example, sudo yum -y install httpd.)
  4. The instance doesn't crash or show any errors that aren't present in a bare-metal system