Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Earth - Ana #47

Open
wants to merge 47 commits into
base: master
Choose a base branch
from
Open

Earth - Ana #47

wants to merge 47 commits into from

Conversation

anakp07
Copy link

@anakp07 anakp07 commented Nov 17, 2020

Media Ranker

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Describe a custom model method you wrote. I wrote the spotlight method, which take a work as parameter and its votes and returns the piece of work with the highest votes.
Describe how you approached testing that model method. What edge cases did you come up with? I made sure that it worked with any votes, and also tested that it would return nil if there were no votes in the system.
What are session and flash? What is the difference between them? Sessions are used to keep track of a specific user on page (when they log-in/log-out). Flash is used to send one-time messages to user regarding status of actions.
What was one thing that you gained more clarity on through this assignment? Testing. Its always my weak point but slowly I feel like I understand more.
What is the Heroku URL of your deployed application? I didnt have time to deploy -- I'll try and do it even though the assignment is already turned in.

Assignment Submission: Media Ranker

Congratulations! You're submitting your assignment. Please reflect on the assignment with these questions.

Reflection

Prompt Response
What was a custom model method you wrote? What was it responsible for doing?
Describe how you approached testing that model method. What edge cases did you come up with?
What are session and flash? What is the difference between them?
What was one thing that you gained more clarity on through this assignment?
What is the Heroku URL of your deployed application?

anakp07 and others added 30 commits November 9, 2020 15:03
…ks and began to work on Works Controller methods
Copy link

@CheezItMan CheezItMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Media Ranker

Functional Requirements: Manual Testing

Criteria yes/no
Before logging in --
1. On index page, there are at most 10 pieces of media on three lists, and a Media Spotlight ✔️, although you have a small bug, see my inline comments
2. Can go into a work's show page ✔️
3. Verify unable to vote on a work, and get a flash message ✔️
4. Can edit this work successfully, and get a flash message ✔️
5. Can go to "View all media" page and see three lists of works, sorted by vote ⚠️ the works are displayed, but not sorted by votes, see my inline notes.
6. Verify unable to create a new work when the form is empty, and details about the validation errors are visible to the user through a flash message ⚠️, Mostly right, but you're only giving 1 validation error however. You might in the future have multiple validation errors.
7. Can create a new work successfully. Note the URL for this work's show page ✔️
8. Can delete this work successfully ✔️
9. Going back to the URL of this deleted work's show page produces a 404 or some redirect behavior (and does not try to produce a broken view) ✔️
10. Verify that the "View all users" page lists no users ✔️
Log in --
11. Logging in with a valid name changes the UI to "Logged in as" and "Logout" buttons ✔️
12. Your username is listed in "View all users" page ✔️
13. Verify that number of votes determines the Media Spotlight ✔️
14. Voting on several different pieces of media affects the "Votes" tables shown in the work's show page and the user's show page ✔️
15. Voting on the same work twice produces an error and flash message, and there is no extra vote ✔️
Log out --
16. Logging out showed a flash message and changed the UI ✔️
17. Logging in as a new user creates a new user ✔️
18. Logging in as an already existing user has a specific flash message ✔️

Major Learning Goals/Code Review

Criteria yes/no
1. Sees the full development cycle including deployment, and the app is deployed to Heroku ⚠️, not deployed
2. Practices full-stack development and fulfilling story requirements: the styling, look, and feel of the app is similar to the original Media Ranker ✔️, this mostly the case, you didn't have the layout on the homepage done.
3. Practices git with at least 25 small commits and meaningful commit messages ✔️

Previous Rails learning, Building Complex Model Logic, DRYing up Rails Code

Criteria yes/no
4. Routes file uses resources for works ✔️
5. Routes file shows intention in limiting routes for voting, log-in functionality, and users ✔️
6. The homepage view, all media view, and new works view use semantic HTML ✔️
7. The homepage view, all media view, and new works view use partials when appropriate ✔️, you are using a partial, but only for the form. See my inline comments
8. The model for media (likely named work.rb) has_many votes ✔️
9. The model for media has methods to describe business logic, specifically for top ten and top media, possibly also for getting works by some category ✔️, yes, but see my inline comments for bugs
10. Some controller, likely the ApplicationController, has a controller filter for finding a logged in user ⚠️ No controller filters
11. Some controller, likely the WorksController, has a controller filter for finding a work ⚠️ No controller filters
12. The WorksController uses strong params ✔️
13. The WorksController's code style is clean, and focused on working with requests, responses, params, session, flash ✔️ for the most part but you have a missing flash notice in works for update and you only show a maximum of 1 validation message...

Testing Rails Apps

Criteria yes/no
14. There are valid fixtures files used for users, votes, and works ✔️
15. User model has tests with sections on validations (valid and invalid) and relationships (has votes) ✔️
16. Vote model has tests with sections on validations (valid and invalid) and relationships (belongs to a user, belongs to a vote) ✔️
17. Work model has tests with sections on validations (valid and invalid) and relationships (has votes) ✔️
18. Work model has tests with a section on all business logic methods in the model, including their edge cases ⚠️ Yes, but you're missing some test cases

Overall Feedback

Overall Feedback Criteria yes/no
Yellow (Approaches Standards) 12+ in Functional Requirements: Manual Testing && 11+ in Code Review, or the instructor judges that this project needs special attention 💛

Code Style Bonus Awards

Was the code particularly impressive in code style for any of these reasons (or more...?)

Quality Yes?
Perfect Indentation
Descriptive/Readable

Summary

Not bad Ana. You had some bugs, including one that stopped the homepage from loading. Take a look at my inline comments for more feedback. Things to work on include, testing more than just that something is invalid for validation errors, you want to know why it's invalid as well. You also need more through testing of model methods and controller actions. Also avoid pulling model data directly with the views, let the controller decide what data needs to get drawn and the view can work on just displaying that data.

ou did a pretty good job with testing, seems like a big improvement. You also had a lot of the functionality in place. You just had a few additional bugs. The html/css also looks pretty good overall.

Areas to work on:

  1. Covering edge-cases in tests and testing more than just validity for validations.
  2. Using Partial Views effectively
  3. Review my comments on your model methods for things to avoid.
  4. Use controller filters for things like the current user or current work.

Not a perfect solution, but not a bad one either. Definitely some growth here. Well done.

Comment on lines +3 to +5
resources :works #Nested Routes --
# resources :votes, only: [:create]
# end

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious why you didn't do this, but did the same route as a custom route on line 14?

@@ -0,0 +1,21 @@
class Work < ApplicationRecord
validates :title, presence: true, uniqueness: true
validates :media, presence: true

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a note that you can have another validation to make sure the category is one of a list.

has_many :votes

def self.spotlight
return nil if self.nil?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean this?

Suggested change
return nil if self.nil?
return nil if self.all.length == 0

end

def self.top_ten(media)
return nil if self.nil?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In a class method self.nil? can never be true because the class Work is never going to be nil.

def self.top_ten(media)
return nil if self.nil?

top_media = Work.where(media: media.to_s)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

if user.save
flash[:welcome] = "Welcome #{user.username}"
else
render :new, status: :bad_request

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should be rendering the login_form view because you don't have a new view.

must_respond_with :success
end

describe "logging in" do

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about a test if the user submits an invalid user name (blank).

@@ -0,0 +1,84 @@
require 'test_helper'
require 'pry'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is included via the Gemfile. You don't need to require it.

Suggested change
require 'pry'

redirect_to work_path(@work)
return
else
render :edit, status: :bad_request

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No flash notices?

Comment on lines +34 to +42
<% if session[:user_id] %>
<li class = "nav-item app-header__nav_item">
<%= button_to "Logout", logout_path, method: :post, class: "btn btn-primary" %>
</li>
<%else %>
<li class = "nav-item app-header__nav_item">
<%=button_to "Log in", login_path, method: :get %>
</li>
<%end %>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is something I would replace with an @user using a controller filter to find the current user. That way the view doesn't have to know anything about session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants