ithill22 / draft_madness_be Goto Github PK

• This endpoint should follow the pattern of DELETE /api/v0/user_league, and it should destroy an existing association between a user and a league.
• The user_id and the league_id should be passed in via the body.
• When a UserLeague resource can be found with the passed in user_id and league_id, that resource should be destroyed, and a response will be sent back with a 204 status, with nothing returned in the body of the request.
• After implementing the happy path for this endpoint, run it, and check that when you call GET /api/v0/users/:id/leagues for the user in which you just deleted an association to a league, that you don’t see the recently removed league listed.

• This endpoint should follow the pattern of GET /api/v0/teams
• A JSON object is return with a top level key that points to a collection of teams in the tournament and their attributes.

• This end point should follow the pattern of POST /api/v0/user and should pass ALL attributes required to create a user (username, email, and password_digest) as JSON in the body of the request.
• This end point should create a new user
• A successful response will return a response of a 201 status code, and return the newly created user
• If any number of attributes are left out in the body of the request, a status code of 400, as well as a descriptive error message should be sent back in the response.

• This endpoint should follow the pattern of GET /api/v0/leagues
• If a valid user id is passed in, a JSON object is sent back with a key that points a collection of that user's leagues. Each league contains all of its attributes.

As a registered user, when I visit the welcome page,
I see a button to sign in as an existing user.
When I click the button, I am taken to a user login page.

(Where do we go after user login?) Dashboard?

• This endpoint should follow the pattern of POST /api/v0/user_leagues, and should pass ALL attributes required to create a league (league_id, user_id).
• When valid ids for User and League are passed in, a UserLeague will be created, and a response will be sent back with a 201 status, detailing that a User was added to a League.
• After implementing the happy path for this endpoint, run it, and check that when you call GET /api/v0/users/:id/leagues for the user in which you just added to a league, that you see the newly associated league listed.
• If there already exists a UserLeague with that user_id and that market_id, a response with a 422 status code and a message informing the client that that association already exists, should be sent back.

• This endpoint should follow the pattern of PATCH /api/v0/league/:id, and can pass any number and combination of attributes to be updated (name, draft_time, draft_date) as JSON in the body of the request.
• This endpoint should update an existing league with any parameters sent in via the body.
• If someone were to try to update a league resource to have a nil or empty attribute, a proper 400-level status code as well as a descriptive error message should be sent back in the response.
• A successful response will return the newly updated vendor resource.

As a visitor, when I visit the welcome page:
I see a button to Sign Up
When I click the Sign Up button,
I am taken to the New User page.

When I fill out all fields with valid information and click Submit,
I am taken to the User Dashboard.

• This endpoint should follow the pattern of GET /api/v0/teams/:id
• If a valid teams id is passed in, all team attributes should be returned

• This endpoints should follow the pattern of GET /api/v0/user_leagues/:id/teams
• If a valid id is passed in, a JSON object is returned that has a key that points to a collection of that user_leagues (rosters) teams

Sad path testing for:

• Create League
• Get All Leagues for a User
• Get One League
• Update a League
• Destroy a League

• This endpoint should follow the pattern of GET /api/v0/league /:id.
  Happy Path
• If a valid league id is passed in, all league attributes should be returned.

get '/api/v0/articles'

• This endpoint should follow the pattern of GET /api/v0/users/:id.
• If a valid market id is passed in, all user attributes should be returned.

• This end point should follow the pattern of POST /api/v0/roster_teams, and should pass ALL attributes required to create a roster_team(user_league_id, and api_team_id) as a JSON in the body of the request.
• This endpoint should create a new roster_team(pick)

• This endpoint should follow the pattern of DELETE /api/v0/leagues, and it should destroy any existing associations
• The league_id should be passed in via the body.
• When a league resource can be found with the passed in league_id, that resource should be destroyed, and a response will be sent back with a 204 status, with nothing returned in the body of the request.
• After implementing the happy path for this endpoint, run it, and check that when you call GET /api/v0/users/:id/leagues for the user in which you just deleted an association to a league, that you don’t see the recently removed league listed.