# Call for testing of elm-explorations/test 2.0.0

**URL:** <https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458>\
**Category:** Request Feedback\
**Created:** [June 20, 2022, 5:07pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458 "2022-06-20T17:07:05Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Janiczek](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/janiczek/32/4516_2.png) [@Janiczek](https://discourse.elm-lang.org/u/Janiczek)\
**Post date:** [June 20, 2022, 5:07pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458/1 "2022-06-20T17:07:05Z")

</div>

Hello everybody,

the `elm-explorations/test` 2.0.0 release is just around the corner! 🎉

It brings (among other things) a rewrite of the Fuzz module and of the underlying fuzzing / shrinking machinery. That gives users a lot of nice API improvements (eg. `Fuzz.andThen`), and we’d like you to test the 2.0.0 version on your test suites and give feedback before the release gets published for everybody.

* * *

On that note, we’ve added a new pair of commands to `elm-test` to help with that:

- **`elm-test install-unstable-test-master`**
  - which will install `elm-explorations/test @ master` in place of the `1.2.2` version in your `ELM_HOME`

- **`elm-test uninstall-unstable-test-master`**
  - which will undo that

To gain access to these commands and more improvements, upgrade to the `0.19.1-revision8` version of `elm-test` runner with:

```auto
$ npm install elm-test@0.19.1-revision8

```

(More information about the `elm-test` release in @lydell’s post: [Elm-test 0.19.1-revision8 released!](https://discourse.elm-lang.org/t/elm-test-0-19-1-revision8-released/8457))

* * *

To give you an idea about what’s coming in `elm-explorations/test 2.0.0`, here is the full commented API diff between `1.2.2` and `2.0.0`: [elm-test 2.0.0 upgrade guide · GitHub](https://gist.github.com/Janiczek/2e5cf91694851866fda9089d649baad9)

We hope you’ll like it!

---

<div class="post-metadata">

**Author:** ![harmboschloo](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/harmboschloo/32/3563_2.png) [@harmboschloo](https://discourse.elm-lang.org/u/harmboschloo)\
**Post date:** [June 20, 2022, 5:42pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458/2 "2022-06-20T17:42:53Z")

</div>

I gave this a quick try on two work projects.

First one has 501 tests, but with the upgrade I got this compile error

> Compiling  
> – ERROR -----------------------------------------------------------------------
> 
> I ran into something that bypassed the normal error reporting process! I  
> extracted whatever information I could from the internal error:
> 
> > Map.!: given key is not an element in the map  
> > CallStack (from HasCallStack):  
> > error, called at libraries\containers\Data\Map\Internal.hs:610:17 in containers-0.5.11.0:Data.Map.Internal
> 
> These errors are usually pretty confusing, so start by asking around on one of  
> forums listed at [community](https://elm-lang.org/community) to see if anyone can get you  
> unstuck quickly.
> 
> – REQUEST ---------------------------------------------------------------------
> 
> If you are feeling up to it, please try to get your code down to the smallest  
> version that still triggers this message. Ideally in a single Main.elm and  
> elm.json file.
> 
> From there open a NEW issue at [Issues · elm/compiler · GitHub](https://github.com/elm/compiler/issues) with your  
> reduced example pasted in directly. (Not a link to a repo or gist!) Do not worry  
> about if someone else saw something similar. More examples is better!
> 
> This kind of error is usually tied up in larger architectural choices that are  
> hard to change, so even when we have a couple good examples, it can take some  
> time to resolve in a solid way.elm.EXE: Map.!: given key is not an element in the map  
> CallStack (from HasCallStack):  
> error, called at libraries\containers\Data\Map\Internal.hs:610:17 in containers-0.5.11.0:Data.Map.Internal
> 
> `elm make` failed with exit code 1.

The second project had 43 tests and that ran without a problem.

---

<div class="post-metadata">

**Author:** ![Janiczek](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/janiczek/32/4516_2.png) [@Janiczek](https://discourse.elm-lang.org/u/Janiczek)\
**Post date:** [June 20, 2022, 5:48pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458/3 "2022-06-20T17:48:57Z")

</div>

Hey @harmboschloo, thanks for trying the library out!

As for the error, that’s a hard one to debug. Elm 0.19.1 has dealt with most of these, but it seems like you found a way to trigger it 🙂

Based purely on a hunch, could you please try to remove `elm-stuff` and `~/.elm` before running the `elm-test install-unstable-test-master` and `elm-test` commands again?

---

<div class="post-metadata">

**Author:** ![harmboschloo](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/harmboschloo/32/3563_2.png) [@harmboschloo](https://discourse.elm-lang.org/u/harmboschloo)\
**Post date:** [June 20, 2022, 6:10pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458/4 "2022-06-20T18:10:09Z")

</div>

> [@Janiczek](#):
>
> Based purely on a hunch, could you please try to remove `elm-stuff` and `~/.elm` before running the `elm-test install-unstable-test-master` and `elm-test` commands again?

Yes that helped.

Seems the problem is that we have `avh4/elm-program-test` in our direct dependencies and `elm-explorations/test` also in our indirect dependencies. Not sure if I can work around that, or why that would be a problem though. 🤔

> – PROBLEM BUILDING DEPENDENCIES -----------------------------------------------
> 
> I ran into a compilation error when trying to build the following package:
> 
> ```
> avh4/elm-program-test 3.6.3
> 
> ```
> 
> This probably means it has package constraints that are too wide. It may be  
> possible to tweak your elm.json to avoid the root problem as a stopgap. Head  
> over to [community](https://elm-lang.org/community) to get help figuring out how to take this  
> path!

---

<div class="post-metadata">

**Author:** ![Janiczek](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/janiczek/32/4516_2.png) [@Janiczek](https://discourse.elm-lang.org/u/Janiczek)\
**Post date:** [June 20, 2022, 6:39pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458/5 "2022-06-20T18:39:33Z")

</div>

That’s likely a consequence of disguising the `master` version of elm-test as `1.2.2`. We likely won’t be able to betatest this + elm-program-test together unless you want to go patching your local copy of elm-program-test inside ~/.elm 🙂

Thanks for trying!

---

<div class="post-metadata">

**Author:** ![harmboschloo](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/harmboschloo/32/3563_2.png) [@harmboschloo](https://discourse.elm-lang.org/u/harmboschloo)\
**Post date:** [June 20, 2022, 7:04pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458/6 "2022-06-20T19:04:24Z")

</div>

Yeah, makes sense. I did try another project with 1000+ tests and that worked fine.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [June 30, 2022, 7:04pm UTC](https://discourse.elm-lang.org/t/call-for-testing-of-elm-explorations-test-2-0-0/8458/7 "2022-06-30T19:04:51Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.