avh4/elm-format

Tests should not fail on Windows (fails on bad/Empty.elm)

Open

#180 opened on May 20, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Haskell (1,329 stars) (148 forks)batch import
help wantedplatform: Windows

Description

No error message is printed, so need to figure out why it's happening and then fix it.

Contributor guide

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.
3
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.
needs investigation
Prerequisites
familiarity with HaskellWindows environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate why tests fail on Windows with 'bad/Empty.elm'. The error is not printed, so the first step is to reproduce the failure locally on Windows. Check the test configuration and see if there are any platform specific issues in the test runner or the elm format code. Look at the CI setup (if any) for Windows builds. Examine the 'bad/Empty.elm' file to understand its structure and why it might cause a failure only on Windows. Consider file path differences (backslashes vs. forward slashes) or line ending differences.