Test failure: "key \"evidence_due_by\" not present"

[chris-martin]

   Event tests
      Succesfully retrieves events FAILED [1]

    Failures:

      tests/Web/Stripe/Test/Event.hs:15:
      1) Event tests Succesfully retrieves events
           predicate failed on: Left (StripeError {errorType = ParseFailure, errorMsg = "key \"evidence_due_by\" not present", errorCode = Nothing, errorParam = Nothing, errorHTTP = Nothing})

    Randomized with seed 981717192

Stripe's changelog indicates that evidence_due_by was replaced by evidence_details in 2014.

[bsima]

I started work on this but couldn't figure out how to run the tests. @dmjio any advice?

[ben@lithium:~/src/stripe]$ nix-shell default.nix --attr stripe-haskell
these paths will be fetched (0.01 MiB download, 0.03 MiB unpacked):
.....
[nix-shell:~/src/stripe]$ stack test
stripe-http-streams-2.3.0: test (suite: tests)
stripe-http-streams-2.3.0: Test suite tests failed
Log files have been written to: /home/ben/src/stripe/.stack-work/logs/
Test suite failure for package stripe-http-streams-2.3.0
    tests:  exited with: ExitFailure 1
Full log available at /home/ben/src/stripe/.stack-work/logs/stripe-http-streams-2.3.0-test.log


    Please enter your Stripe *TEST* account
    tests: <stdin>: hGetLine: end of file


[nix-shell:~/src/stripe]$ 

[dmjio]

First step would be to get into a shell for stripe-http-streams (stripe-tests is used in the test suite of stripe-http-streams). Next step would be to ensure dependencies are all correct (contingent on your nixpkgs version). Bump the upper bounds if need be. Then once you can cabal configure —enable-tests, run “cabal test” in that shell.

Sent from my iPhone

On May 11, 2018, at 5:19 PM, Ben Sima [email protected] wrote:

I started work on this but couldn't figure out how to run the tests. @dmjio any advice?

[ben@lithium:~/src/stripe]$ nix-shell default.nix --attr stripe-haskell these paths will be fetched (0.01 MiB download, 0.03 MiB unpacked): ..... [nix-shell:~/src/stripe]$ stack test stripe-http-streams-2.3.0: test (suite: tests) stripe-http-streams-2.3.0: Test suite tests failed Log files have been written to: /home/ben/src/stripe/.stack-work/logs/ Test suite failure for package stripe-http-streams-2.3.0 tests: exited with: ExitFailure 1 Full log available at /home/ben/src/stripe/.stack-work/logs/stripe-http-streams-2.3.0-test.log

Please enter your Stripe *TEST* account
tests: <stdin>: hGetLine: end of file

[nix-shell:~/src/stripe]$ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[bsima]

Okay, I think it's working, thanks for the help. I'll write up a CONTRIBUTING.md with this info to try and help newcomers.

David Johnson [email protected] writes:

First step would be to get into a shell for stripe-http-streams (stripe-tests is used in the test suite of stripe-http-streams). Next step would be to ensure dependencies are all correct (contingent on your nixpkgs version). Bump the upper bounds if need be. Then once you can cabal configure —enable-tests, run “cabal test” in that shell.

Sent from my iPhone

On May 11, 2018, at 5:19 PM, Ben Sima [email protected] wrote:

I started work on this but couldn't figure out how to run the tests. @dmjio any advice?

[ben@lithium:~/src/stripe]$ nix-shell default.nix --attr stripe-haskell these paths will be fetched (0.01 MiB download, 0.03 MiB unpacked): ..... [nix-shell:~/src/stripe]$ stack test stripe-http-streams-2.3.0: test (suite: tests) stripe-http-streams-2.3.0: Test suite tests failed Log files have been written to: /home/ben/src/stripe/.stack-work/logs/ Test suite failure for package stripe-http-streams-2.3.0 tests: exited with: ExitFailure 1 Full log available at /home/ben/src/stripe/.stack-work/logs/stripe-http-streams-2.3.0-test.log

Please enter your Stripe TEST account tests: : hGetLine: end of file

[nix-shell:~/src/stripe]$ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.