Explore
For Enterprise
Join for Free
Log In

예술 & 인문학
비즈니스
컴퓨터 공학
데이터 과학
정보 기술
건강
수학 및 논리
자기개발
물리 과학 및 공학
사회 과학
언어 학습
Institute for the Future
Learn how to spot opportunities for innovation and invention
Master essential foresight techniques with the new Futures Thinking Specialization.
University of Illinois
Interested in earning a top-ranked MCS in Data Science degree?
Join the 1/8 webinar and learn more about how University of Illinois can help you grow your data science career.
학위
수료증

전체 Coursera 둘러보기

검색
Top Courses
포 엔터프라이즈 (For Enterprise)
로그인
무료 회원 가입

Module 3 Introduction

Loading...

Capstone: Photo Tourist Web Application

존스홉킨스대학교

4.8(21개의 평가) | 320명의 학생이 등록함

Ruby on Rails Web Development 전문 분야에서 6의 강좌 6

In this Capstone project for the Photo Tourist you will implement a Ruby on Rails web application that makes use of both a relational and NoSQL database for the backend and expose the data through services to the Internet using Web services and a responsive user interface operating in a browser from a desktop and mobile device. You will have a chance to revisit and apply what you have learned in our previous courses to build and deploy a fully functional web application to the cloud accessible to your co-workers, future employers, friends, and family. In developing the Photo Tourist web application, you will get to work with different data types and data access scenarios (e.g., fielded data display and update, image upload/download, text search, access controlled information) to provide your users the ability to show off their photos and information from trips they have taken and to seek out photos and information from trips taken by others. Using the application you develop, your users will be able to • Create an account • Upload and download photos to the site and make them accessible to others • Provide descriptions of trips and photos that others can read • Organize photos by location and trip, • Find photos based on location • Find photos based on text searches of descriptions • Locate the place where the photo was taken on a map

강의 계획서 보기

배우게 될 기술

Ruby On Rails, Angularjs, Web Development

검토

4.8(21개의 평가)

5 stars
16 ratings
4 stars
5 ratings

EA

Apr 15, 2017

Great Course Jim has really thought me more than enough to get my career started. All a student has to do is just study.

KT

May 04, 2017

Excellent course. Mr. Stafford is a very good teacher.

수업에서

Testing

In this module, you will learn how to development model, request, and feature specs using RSpec and to leverage gems like DatabaseCleaner, FactoryGirl, and Faker in building those specs. You will also learn how to DRY their tests using RSpec shared_contexts and shared_examples as well as Ruby modules for helper methods. All use of tests within the capstone will be "integration-style" tests, going to the database and back. We will not have time to implement pure unit tests for individual components. For model testing, we will focus tests on factories, query scopes, relationships, and facade methods interacting directly with PostgreSQL and MongoDB databases. We will address the general purpose and custom techniques for managing the database state during cleanup. For API testing, we will form a hefty set of RSpec shared_contexts and Ruby helper methods for the request specs that will take care of the details of many CRUD behaviors and other tedious, repetitive tasks. The API is not only easier to test than the Web UI, it is a first-class external interface deserving of separate testing. During test coverage, you will learn internal Rails error handling techniques that will provide the web client a proper and sane web reply in the face of errors. For Web UI testing, we will introduce Capybara for building feature tests and the role of the RackTest, Selenium, and Poltergeist/PhantomJS drivers for implementing UI testing with Javascript. Although Capybara provides a nice interface for expressing Web UI tests, the asynchronous nature of Web UIs make them extremely difficult to test without well thought out decisions during development. This course has a special emphasis on teaching you how to develop automated integration tests at all levels of the architecture, including the Web UIs. It is recommended that you review this module and sample further test-related lectures in follow-on modules to get a good understanding of how testing can best be leveraged in a full stack development (within constraints of the course). Except for the seasoned RSpec and Capybara user, there is no shortcut through this module.

Module 3 Introduction4:19

Spec Anatomy Part 1: Database Interaction and Blocks6:25

Spec Anatomy Part 2: Thinning Examples5:32

Spec Anatomy Part 3: Pending Examples and Lazy/Eager Let Blocks6:08

RSpec with Mongoid9:55

DatabaseCleaner with ActiveRecord6:40

DatabaseCleaner and SharedContexts5:46

DatabaseCleaner with Mongoid5:32

DatabaseCleaner Optimizations5:59

FactoryGirl and Faker6:07

FactoryGirl Factories10:21

FactoryGirl and Faker Data9:01

강사:

Jim Stafford
Adjunct Professor, Graduate Computer Science

스크립트

[MUSIC] Hey, good morning, welcome back. Did you have fun with the last module with all the UI development choices? Just know, the cap zone, you can use any of the options that I demonstrated last week. But as I move forward, from this module forward, my examples will be primarily focused at the asset pipeline. But you saw how easy it was to copy those over. And as long as we conform to a certain number of conventions, we really don't have to worry that much about moving from development to production. So the topic this week is testing. We want to learn more about testing before we develop our complex code. We want to now what to test, how to test, and the gotchas that come along. We'll not only test our code, we'll find a few errors and we'll fix it. We'll bring in several tools, like RSpec, a DSL, a domain-specific language for testing. And with testing, you're going to want to get your database in a known state. So we'll bring in Database Cleaner to give us some transactional and truncation database cleanup strategies. So as our objects get more complex, our tests aren't going to want to worry about the details of what it takes to create some of our objects. So we'll bring in Factory Girl to extract away those required fields and relationships that might be there. And we'll also bring in the Faker Gem to insert some simulated data. We're going to treat our test code as if it were production, and try to dry it as much as possible. To do that, we'll take advantage of RSpec's shared context and shared examples. We're going to treat our test code with some of the same care we do with our application code, and try dry it as much as possible. And we'll leverage RSpecs, shared context, and shared examples, where we can build abstract test artifacts and plug them into concrete test box. And we'll leverage Ruby Modules, to build helper methods around some complex application interactions, like login and logout, that we don't want to repeat everywhere. RSpec gives us many different types of tests that we can execute. I'd like to categorize them into two categories, unit and integration. With unit tests, the item under test is isolated, and we bring in things like stubs and mocks, and focus our testing specifically on that item. It tends to be very efficient, but isolated. With integration tests, we're going to take the item under test and put it in the flow. We're going to take some point in the application and go to the database and back. It may take a little bit longer to execute the test, and we might be a little bit more limited in what we can test. But we'll come away with a degree of confidence that what we have works in the overall flow of the operation. Because in the capstone we have a limited amount of time that we have for testing. But we can't do without it. Testing does give us a convenient platform to demonstrate our code, but it also makes sure that it works before we move on. And the regression testing will also point out if we break something while we're implementing a feature down the road. Our specific types are going to be model, request, and feature specs. With model specs we're going to focus on query scopes, facade methods, and relationships. We're going to assume that ActiveRecord and Mongoid work, we don't need to test those. With request backs, we're going to evaluate the APIs for its functionality and the payload concepts before we build the UI on top of it. It's much easier to test the API and make sure that's sound before we bring in the user interface. With feature specs we're going to use Capybara to test the web UI and bring in two drivers to do that, Selenium and PhantomJS with the poltergeist gem. Selenium is a good choice for authoring, where can see the interaction with the browser, keystrokes, button clicks, fields being filled in. Where Poltergeist and PhantomJS have a nice headless solution, where we can use that more for regression testing. For things we have finished and we want to make sure that we haven't broken anything. I will point out, though, that that testing asynchronous applications like the Web UI is a very complex thing to do. It's going to take a good bit of knowledge and good decisions in order to come out with deterministic results. This is the last warm up module before we start developing the application code that's part of the capstone, so we want to make sure you get these concepts well understood before we get into that more complicated code, okay? So put your stuff down and let's get started.

Coursera 카탈로그 살펴보기

무료로 참여해 맞춤화된 추천, 업데이트 및 제안을 받아보세요.

Coursera provides universal access to the world’s best education, partnering with top universities and organizations to offer courses online.

© 2019 Coursera Inc. All rights reserved.

Coursera
소개
리더십
직업
카탈로그
수료증
MasterTrack™ 수료증
학위
포 엔터프라이즈 (For Enterprise)
정부용
캠퍼스용

커뮤니티
Learners
Partners
Developers
Beta Testers
Translators

연결
블로그
Facebook
Linkedin
Twitter
Instagram
YouTube
기술 블로그

기타
조건
개인정보 보호
도움말
접근성
보도 자료
문의하기
디렉토리
계열사