"Little Esty Shop" is a group project that requires students to build a fictitious e-commerce platform where merchants and admins can manage inventory and fulfill customer invoices.

• Practice designing a normalized database schema and defining model relationships
• Utilize advanced routing techniques including namespacing to organize and group like functionality together.
• Utilize advanced active record techniques to perform complex database queries
• Practice consuming a public API while utilizing POROs as a way to apply OOP principles to organize code

• Must use Rails 7.0.x, Ruby 3.2.2
• Must use PostgreSQL
• All code must be tested via feature tests and model tests, respectively
• Must use GitHub branching, team code reviews via GitHub PR comments, and either GitHub Projects or a project management tool of your group's choice (Trello, Notion, etc.)
• Must include a thorough README to describe the project
  • README should include a basic description of the project, a summary of the work completed, and some ideas for a potential contributor to work on/refactor next. Also include the names and GitHub links of all student contributors on your project.
• Must deploy completed code to the internet (using Heroku or Render)
• Continuous Integration / Continuous Deployment is not allowed
• Use of scaffolding is not allowed
• Any gems added to the project must be approved by an instructor
  • Pre-approved gems are capybara, pry, faker, factory_bot_rails, orderly, simplecov, shoulda-matchers, launchy

• Fork this repository
• Clone your fork
• From the command line, install gems and set up your DB:
  • bundle
  • rails db:create
• Run the test suite with bundle exec rspec.
• Run your development server with rails s to see the app in action.

1. Database Setup
2. User Stories
3. Extensions
4. Evaluation

• For this project we had to come together as a group to build a web application that allowed the user to manipulate data for merchants, items, invoices, transactions, and other useful information pertaining to running an ecommerce site. We were able to get through all the user stories, cutting it right up to the wire for the API stories. There are many lessons that we have taken away as both individuals and a collective working group, least of which includes don't wait to merge until the day of submission. I think our CSS styling leaves much to be desired and we encountered some very funky issues in our testing. Oftentimes bundle exec rspec runs fully passing but will occasionally show failing tests for reasons none of us were able to fully comprehend. We found that running rails db:{drop,create,migrate} would occasionally work and that quitting VS and starting it back up would usually bring our tests back to fully passing.

Ian - https://github.com/ILyell Connor - https://github.com/ConnorRichmond Wil - https://github.com/fadwil Parker - https://github.com/ParkerBoeing