Ryan Elliott 1-1 about beerme

[RyanElliott10]

Am I blocked?

No.

What I did. (Use links to GH Issues as appropriate)

Completed the UI wireframes, as per #17. Furthermore, I familiarized myself React to ensure we can begin the development of the website starting next week.

What I plan to do next week. (It's okay if you don't know or if things change. Just take a guess)

We will begin coding the frontend of the website next week, focusing on the homepage to start simple. Additionally, we will begin testing connecting the website to the database.

[RyanElliott10]

Am I blocked?

No.

What I did. (Use links to GH Issues as appropriate)

Implemented the skeleton for the Explore page, per issue #35. In addition to this, I created multiple reusable components such as the website header and the main buttons we will be using throughout the website.

What I plan to do next week. (It's okay if you don't know or if things change. Just take a guess)

Next week, we will develop the login page to test the user account creation and login flow with the backend. To work on this, however, we will need to connect the frontend and backend, a task we have yet to devote much time to.

[RyanElliott10]

Am I blocked?

No.

What I did. (Use links to GH Issues as appropriate)

Added a fair bit of functionality to the website. First and foremost, I added a true login/account creation page, as can be found in this PR, and various others, fixing the formatting and styling.

Additionally, I added a new styler to the website, react-boostrap, to make it look far more finished than previously. After this, I had a number of pull requests adding validation logic to form submissions, and we were finally able to successfully verify the frontend's capability to speak to the database.

What I plan to do next week. (It's okay if you don't know or if things change. Just take a guess)

Next week, we will continue the development of the login page and begin building out the account page. Additionally, I will add logic to the Explore page to allow users to actually progress through the selection process and truly communicate with the server rather than relying on dummy data.

[RyanElliott10]

Am I blocked?

Partially; we're facing difficulties getting the backed up and running on a remote server so the frontend is not able to communicate with the database without a local server running.

What I did. (Use links to GH Issues as appropriate)

I was able to finalize the user's login/create account flow and send the appropriate data up to the backed. I additionally added pagination to the explore page, allowing the user to select their preferences and send make POST calls to store this data in the database.

What I plan to do next week. (It's okay if you don't know or if things change. Just take a guess)

I will be working with Vedant and Isaac to get the backed hooked up to a remote server to allow the frontend to communicate without the crutch of a local server.

[RyanElliott10]

Am I blocked?

Somewhat; the backend has been pushed for time and have not been able to get the database on a remote service, so it'll be difficult to test and verify our website's functionality. However, we will be able to overcome this by working closely together.

What I did. (Use links to GH Issues as appropriate)

I added a new page, Account Details, to allow users to view their account's information and settings #74 . This also allows business accounts to create new beers to be added to our database. Additionally, I got our UI automation tests up and running using Selenium (as can be found in #79)

What I plan to do next week. (It's okay if you don't know or if things change. Just take a guess)

I will be continuing work on ensuring the frontend is able to communicate with the backend and will hopefully run a full UI automation test across the entire website to verify the website is bug-free.

[RyanElliott10]

Am I blocked?

Partially. I am not able to access the backend on my computer since the server is ran through localhost and is using a tech stack dependent upon the .NET core framework, something that does not support macOS. I've been using @marinecossoul 's computer to add commits in the meantime.

What I did

I added a final landing page for once the user submits their selections via the Explore feature (#85). Additionally, I added a locked page for the Recommendations page (#93) and managed to add Travis CI to the repo (#89). While adding Travis, I had to fix a few test cases. I've also had various PRs here and there throughout the week with bug fixes and minor feature additions.

What I plan to do next week

The team will be working as a whole to get the final integrations completed. I will also be adding test cases throughout all of the frontend to increase code coverage, and managing any bugs that pop up.