Til Tracker

`FactoryBot::DuplicateDefinitionError` on dev server startup

Context: My development server (./bin/dev) failed to boot, reporting FactoryBot::DuplicateDefinitionError: Factory already registered: learning.
Cause: The factory_bot_rails gem was included in the group :development, :test do block in the Gemfile. This caused FactoryBot's Railtie to load factory definitions (spec/factories/*.rb) during development environment initialization (e.g., via Spring or initial boot), potentially conflicting with other initializers or running twice.
Resolution: I moved gem "factory_bot_rails" exclusively to the group :test do block in the Gemfile and ran rbenv exec bundle install.
Learning: I learned that gems intended solely for testing (like factory_bot_rails, shoulda-matchers, capybara) should typically only be included in the :test group in the Gemfile. Including them in :development can lead to unexpected behavior, errors during server startup, or unnecessary loading as their initializers might run inappropriately or cause conflicts.

Tags: testing dependencies factorybot gemfile environment-setup workflow

Learned on: April 15, 2024 Edit

Observation: Pending model specs for `Learning`

My Observation: RSpec reported pending examples for spec/models/learning_spec.rb.
Context: The generated model spec file contains a placeholder pending test (pending "add some examples to (or delete) /opt/render/project/src/db/seeds.rb").
Resolution: Needs implementation of model tests (e.g., for validations) as per TASK.md.
Learning: Pending specs are reminders from RSpec to write tests for specific files/contexts. They don't indicate errors but highlight missing test coverage. I need to address them by writing tests or removing the spec file if not needed.
Next Step: Implement tests for title and body presence validations, and optionally for the tag_list helper method.

Tags: testing workflow

Learned on: April 14, 2024 Edit

Request spec failures (`StaticPages` 404s)

Context: My request specs failed: StaticPages GET /... returns http success failed with Expected response to be a <2XX: success>, but was a <404: Not Found>. This occurred for /home, /hire_me, /about specs in spec/requests/static_pages_spec.rb. The specs were using hardcoded string paths (e.g., get "/static_pages/home") that didn't match the actual routes defined in config/routes.rb.
Resolution: I updated the specs to use the correct Rails path helpers (get root_path, get hire_me_path, get about_path) defined by config/routes.rb.
Learning: I learned to always use Rails path helpers (e.g., root_path, learnings_path, hire_me_path) in request/system specs instead of hardcoding URL strings. This ensures tests remain accurate even if routes change and avoids simple 404 errors. Using rails routes helps check available helpers.

Tags: testing rails-core rspec request-spec routes path-helpers configuration

Learned on: April 14, 2024 Edit

Request spec failure (`render_template` matcher missing)

Context: My request spec failed: Failure/Error: expect(response).to render_template(:new) ... assert_template has been extracted to a gem. To continue using it, add gem 'rails-controller-testing' to your Gemfile. The render_template matcher in RSpec request specs relies on functionality (assert_template) that is no longer part of Rails core.
Resolution: I added gem 'rails-controller-testing' to the :test group in the Gemfile and ran bundle install.
Learning: I learned to be aware that testing helpers previously included in Rails core might be extracted into separate gems in newer versions. Error messages usually indicate the required gem (rails-controller-testing for render_template, assigns, assert_template).

Tags: testing rails-core rspec request-spec dependencies gem controller-testing gemfile

Learned on: April 14, 2024 Edit

Learnings

`FactoryBot::DuplicateDefinitionError` on dev server startup

Observation: Pending model specs for `Learning`

Request spec failures (`StaticPages` 404s)

Request spec failure (`render_template` matcher missing)