mattlindsey/mythographer

Edit Story: Add a system test for editing a story

Open

#46 opened on Feb 3, 2024

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Ruby (4 forks)auto 404
good first issue

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (PR metrics pending)

Description

Complete the test in spec/system/story_tests_spec.rb for "edits an existing story."
Also feel free to add other tests that you think are useful.

Note: I think after user hits 'Update Story' the site should probably return to the 'show' page and not the 'story list' page.

Contributor guide

Research direction
Open the test file at spec/system/story tests spec.rb and find the incomplete test for editing a story. Run the existing tests to see the failure. Implement the test to simulate editing a story via the UI, then verify the story is updated and the user is redirected to the show page (not the index page). You may also add additional tests for edge cases or different scenarios. Use Capybara matchers and assertions.
Tech stack
ruby
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RubyRails testing basics (RSpec, Capybara)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75