playframework / playframework/play-slick

Exception when unit testing an API call using Slick

Open
#345 37 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status:backlog
Dominant language
Scala
Stars
794
Forks
272
Avg merge
1d 8h
Merged PRs (30d)
17

Description

As noted in https://github.com/playframework/playframework/issues/5466 there is a current issue when unit testing APIs that use Slick

For a minimal repro case, use "activator test" in this project
test.zip

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running "activator test" in the attached minimal reproduction and read the context in Play Framework issue 5466. Trace the exception raised when unit testing an API that uses Slick; done means the reproduction no longer fails with that exception and the relevant test passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
api, databases, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.