avh4 / avh4/elm-program-test

ProgramTest.selectOption gives parsing error "firstErrorOf: couldn't parse failure report: Expecting Keyword ▼ Query.has"

Open
#176 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Elm
Stars
95
Forks
28
PR merge metrics
No merged PRs in 30d

Description

Error given in elm-test
```
▼ ProgramTest.selectOption "state" "State" "UT" "Utah"

✓ check label exists:
✓ has tag "label"
✓ has attribute "htmlFor" "state"
✓ has text "State"
✓ find select:
✓ has tag "select"
✓ has attribute "id" "state"
✗ check option exists:
✗ PLEASE REPORT THIS AT : firstErrorOf: couldn't parse failure report: Expecting Keyword ▼ Query.has at row 843, col 84


Line calling selectOption
```
|> ProgramTest.selectOption "state" "State" "UT" "Utah"
```

My HTML output
`
State



Alabama


Alaska


Arizona


Arkansas


California


Colorado


Connecticut


Delaware


District of Columbia


Florida


Georgia


Hawaii


Idaho


Illinois


Indiana


Iowa


Kansas


Kentucky


Louisiana


Maine


Maryland


Massachusetts


Michigan


Minnesota


Mississippi


Missouri


Montana


Nebraska


Nevada


New Hampshire


New Jersey


New Mexico


New York


North Carolina


North Dakota


Ohio


Oklahoma


Oregon


Pennsylvania


RhodeIsland


South Carolina


South Dakota


Tennessee


Texas


Utah


Vermont


Virginia


Washington


West Virginia


Wisconsin


Wyoming


`

Contributor guide

Open the contributing guide

Research direction

Start at ProgramTest.selectOption and reproduce the failure using the supplied select markup and the "state"/"UT" example. Trace the failure-report parsing path behind the "Expecting Keyword Query.has" message; done means the option assertion runs and reports a normal result instead of a parser error.

Written by the indexing model from the issue text.

Assessment

Tech stack
elm
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.