I, as the user, should only be able to see the authentication screen if I'm logged out. However, if I'm logged in, I should be able to see the rest of the website and NOT the authentication screen. Vice versa.
Acceptance Criteria
AS NOTATED FROM INSTRUCTIONS
[Authentication]
As a user, who is logged out, I should only be able to see the authentication screen
As a user who is logged out, I would like to be able to click on an authentication button and login via google.
As a user who is logged in, I should not be able to see the authentication button.
As a user who is logged in, I should be able to see the Team view.
As a user who is logged in, I should be able to see a log out button
Dependecies
3 - Authentication needs to be setup in order for this to work. Web server should be tested as well.
4 - The test data should take into account user UIDs.
Dev Notes
Authentication concerns as well as any interaction w/ the user object is handled through a custom hook entitled useAuth(). This should be included in your project and is REQUIRED for user specific commands.
Much of the needed authentication functionality is included in the template. You may want to customize what the authentication screen looks like, though, to fit the theme of your project. This feature will be tracked by this issue ticket,
User Story
I, as the user, should only be able to see the authentication screen if I'm logged out. However, if I'm logged in, I should be able to see the rest of the website and NOT the authentication screen. Vice versa.
Acceptance Criteria
AS NOTATED FROM INSTRUCTIONS
Dependecies
3 - Authentication needs to be setup in order for this to work. Web server should be tested as well.
4 - The test data should take into account user UIDs.
Dev Notes