This is an introductory course for the Amazon Device Farm service. In this course, we are going to start with some important terminology. Then we will discuss the Amazon Device Farm service and its features. We will talk about the benefits of the service. Next, we will talk about why we would use the Amazon Device Farm service. And then, we will discuss how to locate the Device Farm service in the AWS console and describe the basic steps for setting it up. Finally, we will discuss a use case scenario for the Amazon Device Farm service.
This is a beginner level course intended for anyone who is interested in learning the basics about the Amazon Device Farm service. Before attending this course, you may want to attend the “Benefits of Cloud Computing," and “Fundamentals of AWS” Learning Paths, or attend the “What is Cloud Computing?” and “Technical Fundamentals of AWS” courses. While these are not required to attend this course, they include helpful concepts that might make the content of this course a little easier to understand.
- Describe the features and benefits of the Amazon Device Farm service.
- Explain when to use the Amazon Device Farm service.
- Locate the Device Farm service option in the AWS console and discuss how to configure it.
- And give examples of use case scenarios for Amazon Device Farm service.
Before we get started on our discussion of the Amazon Device Farm service, we need to discuss some important concepts related to that technology. Let's take a look at some of the tools that developers use during the development process.
An Integrated Development Environment, or IDE, is an application that includes a combination of tools that developers need for application development. At a minimum, developers need code editors, compilers, debugging tools, and build automation tools. While a developer can find and use individual products to support application development, an IDE brings all of these features together to simplify the process.
Continuous Integration, or CI, is a software development practice for code changes of individual developers are frequently integrated into a shared repository. The purpose of a Continuous Integration environment is to provide feedback by verifying code integrations with automated build and automation tests. The goal of a CI is to quickly detect any defects introduced by each integration so that corrective action can be taken as soon as possible.
Sarah is an educator and instructional designer. She started her career doing computer training, Microsoft Certified training, then telephony training for a local Indianapolis start up. She has a passion for helping others to learn and writing engaging content. When she is not working, she loves to travel with her family, walk her dog, or curl up somewhere with a good book.