avh4/elm-program-test

firstErrorOf: couldn't parse failure report

Open

#162 opened on May 4, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Elm (28 forks)github user discovery
help wanted

Repository metrics

Stars
 (95 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Hey Aaron! Got this while hanging with you on Twitch:

Expected one of the following to exist:
    - <button> with text
        > PLEASE REPORT THIS AT <https://github.com/avh4/elm-program-test/issues>: firstErrorOf: couldn't parse failure report: Expecting Keyword tag  at row 77, col 17
    Expecting Keyword text  at row 77, col 17
    Expecting Keyword attribute  at row 77, col 17
    Expecting Keyword containing  at row 77, col 17
    Expecting  ] at row 77, col 17
    Expecting Keyword attribute  at row 77, col 17
    Expecting Keyword containing  at row 77, col 17    Expecting  ] at row 77, col 17
    - <form> with submit <input> with value
        > PLEASE REPORT THIS AT <https://github.com/avh4/elm-program-test/issues>: firstErrorOf: couldn't parse failure report: Expecting Keyword tag  at row 77, col 17
    Expecting Keyword text  at row 77, col 17
    Expecting Keyword attribute  at row 77, col 17
    Expecting Keyword containing  at row 77, col 17    Expecting  ] at row 77, col 17

Here is the project at the commit producing the error: https://github.com/ryannhg/elm-uno/tree/ca8c3719285df279998d47245dab5132ed68b077

You can run npm run test to reproduce this ( or elm-test )

Contributor guide

Research direction
Inspect the 'firstErrorOf' function and trace the parsing of failure reports. The error message indicates a parser failure at a specific location (row 77, col 17) in the failure report string. Look at the code that generates failure reports and the corresponding parser. Use the provided project to reproduce the error and debug the parsing logic.
Tech stack
None
Domain
testing
Issue type
Bug
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitElm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70