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 - Emily #33

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

Earth - Emily #33

wants to merge 72 commits into from

Conversation

emirry
Copy link

@emirry emirry commented Nov 16, 2020

Media Ranker

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
Describe a custom model method you wrote. I wrote a select_spotlight method in my work model to select the media with the highest votes.
Describe how you approached testing that model method. What edge cases did you come up with? I call that method in my spotlight test and expect it to equal the first media in my works.yml
What are session and flash? What is the difference between them? session is a hash-like object that we use to keep track of data throughout a user's login session. Flash is a message a user might receive whether they successfully accomplished something or not.
What was one thing that you gained more clarity on through this assignment? It was great to see how votes played into this project. It was also something I struggled with at the beginning of my project, because I wasn't sure how I'd connect it to works and users. I feel like I'm making progress with testing, although there's more that I could've tested.
What is the Heroku URL of your deployed application? https://emilys-media-ranker.herokuapp.com/

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?

… code by adding self to methods. calling those methods in works controller.
…. learned about form-control but i don't like it
@jmaddox19
Copy link

Media Ranker

Great work!

The homepage seems to have multiple errors, due to something you changed in your very last commit trying to fix heroku things. It's always worth checking everything one last time before you submit :)

Regardless, you made a whole site with so much interactive functionality that supports signin from many users! This is a big deal! I hope you've been able to celebrate this! Especially in a week when you were also moving!

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 When I go to the home page, I see the following Rails error: wrong number of arguments (given 0, expected 1..3) It seems to be related to a syntax error in the content_for helper you're using. However, when I revert the last commit, I am able to see the homepage.
2. Can go into a work's show page ✔️ I got to it by manually typing the url
3. Verify unable to vote on a work, and get a flash message ✔️
4. Can edit this work successfully, and get a flash message Yes, but no flash message. It's configured so that I need to be logged in but that's totally fine.
5. Can go to "View all media" page and see three lists of works, sorted by vote ✔️
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 ✔️ Yes, though the error message is misleading. It says "Oops! Media already exists."
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) There is something funky going on with redirects here. Chrome says localhost redirected you too many times.
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 Deployed site isn't working but we didn't require it anyway
2. Practices full-stack development and fulfilling story requirements: the styling, look, and feel of the app is similar to the original Media Ranker ✔️
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 Yes for form but a missed opportunity for that with the all media and homepage views.
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 ✔️
10. Some controller, likely the ApplicationController, has a controller filter for finding a logged in user ✔️
11. Some controller, likely the WorksController, has a controller filter for finding a work ✔️
12. The WorksController uses strong params ✔️
13. The WorksController's code style is clean, and focused on working with requests, responses, params, session, flash ✔️

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) validations only, no relationships
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 ✔️

Overall Feedback

Overall Feedback Criteria yes/no
Green (Meets/Exceeds Standards) 14+ in Functional Requirements: Manual Testing && 14+ in Code Review ✔️
Yellow (Approaches Standards) 12+ in Functional Requirements: Manual Testing && 11+ in Code Review, or the instructor judges that this project needs special attention
Red (Not at Standard) 0-10 in Code Review or 0-11 in Functional Reqs, or assignment is breaking/doesn’t run with less than 5 minutes of debugging, 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
Elegant/Clever
Descriptive/Readable
Concise
Logical/Organized

redirect_to work_path(@work.id)
return
else
flash.now[:error] = "Oops! Media already exists."

Choose a reason for hiding this comment

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

I love the idea of having more specific messages for specific situations, but surfacing validation messages is a more fool-proof way to do that.
The way this is currently written, it assumes that if something goes wrong, it's because the work already exists when there are other things that can go wrong.

Choose a reason for hiding this comment

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

In fact, when I try to add a duplicate work, I get the following validation message anyway
title has already been taken

Comment on lines +4 to +22
<h4>Albums</h4>
<tr>
<th>Votes</th>
<th>Title</th>
<th>Created By</th>
<th>Published</th>
<th>Upvote</th>
</tr>
<% Work.sort_media('album').each do |album| %>
<tr>
<td><%= album.votes.count %></td>
<td><%= link_to album.title, work_path(album.id) %></td>
<td><%= album.creator %></td>
<td><%= album.publication_year %></td>
<td><%= link_to "Upvote", work_upvote_path(album.id), method: :post, class:"btn btn-primary" %></td>
<% end %>
</tr>
</table>
</div>

Choose a reason for hiding this comment

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

This code is repeated for each type of work three times almost exactly the same, making it a great candidate for a partial view

end
end

describe "spotlight" do

Choose a reason for hiding this comment

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

There's potential for edgecase testing here as well. What should happen when there's a tie? What should happen if there are no votes yet?

Comment on lines +39 to +40
vote = Vote.create(work_id: media, user_id: user)
vote2 = Vote.create(work_id: media, user_id: user_two)

Choose a reason for hiding this comment

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

Suggested change
vote = Vote.create(work_id: media, user_id: user)
vote2 = Vote.create(work_id: media, user_id: user_two)
vote = Vote.create(work: media, user: user)
vote2 = Vote.create(work: media, user: user_two)

This test is failing because the work and user aren't successfully getting tied to these votes. This is because when you use work_id, ActiveRecord actually wants an id. You can instead change the code to what I have above.

Choose a reason for hiding this comment

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

Suggested change
vote = Vote.create(work_id: media, user_id: user)
vote2 = Vote.create(work_id: media, user_id: user_two)
vote = Vote.create(work_id: media.id, user_id: user.id)
vote2 = Vote.create(work_id: media.id, user_id: user_two.id)

You may have seen this before. This would also work.

# @user = User.find_by(id: session[:user_id])
# @username = @user.username

if @user.nil?

Choose a reason for hiding this comment

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

This will always redirect because the above 2 lines are commented out. That's why the controller tests is failing.

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