You are going to build an application that will store information on Instructors and Students. The relationship between Instructors and Students is many-to-many. An Instructor can have many students, and a Student can have multiple Instructors.
- all code should be 100% tested at both the feature and model levels
- you should use a TDD workflow
- you should also follow all MVC conventions.
- Fork this repository
- Clone your fork
- Complete the Prework below
- Push your solution to your forked repository before your scheduled assessment time
Complete the following tasks before the assessment.
First, create the many to many relationship between Instructors and Students
- Instructors should have a name
- Students should have a name, cohort number, and their age
Once you have completed the database setup, complete the following user stories:
User Story 1: Students Index Page
As a user,
When I visit '/students'
Then I see each student in the system including the student's:
- name
- cohort name (1906, 1808, etc.)
- the name of each instructor that they have
User Story 2: Instructor Show Page
As a user,
When I visit the Students Index Page,
Then I see each instructor's name is a link
When I click the link
Then I am taken to an Instructor Show Page where I see the instructor with that id including the instructor's:
- name
- a list of all their students names
- the average age of all their students
| Rails Syntax | MVC | ActiveRecord | Testing and Debugging | |
|---|---|---|---|---|
| 4 | Students effectively use Rails methods or strategies not discussed in class, and can effectively defend their decision to use those tools. | Student strictly adheres to MVC, and can defend decisions of where functionality lives. | Highly effective and efficient use of ActiveRecord beyond what we've taught in class | Prework tests are extremely well organized and nested. Student demonstrates excellent TDD during paired assessment. |
| 3 | Student effectively and independently uses appropriate Rails syntax to complete the user stories | Student adheres to the principles of MVC, with only one infraction. | Students appropriately choose class vs. instance methods. Students can CRUD resources using built in ActiveRecord methods and ActiveRecord associations. | Tests capture the behavior described in the user stories. Student demonstrates use of TDD, but may be prompted by the instructor once or twice. |
| 2 | Student uses appropriate Rails syntax with instructor prompting, or does not complete the paired user story | Student does not adhere to the principles of MVC, demonstrated by up to 3 infractions. Student is able to describe the principles of MVC. | Student needs prompting from instructor in order to use ActiveRecord to CRUD resources, or student makes an incorrect, or inappropriate choice of using a class or instance method. | Tests do not capture the behavior described in the user stories, and/or the student does not demonstrate consistent use of TDD |
| 1 | Student fails to complete one or both of the prework user stories | Student has more than 3 infractions of MVC and/or can not describe the principle of MVC. | Student is unable to CRUD resources using ActiveRecord | Student is unable to write an effective test without significant instructor guidance. |
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent