crisdegraciadev
Hey guys,
I’m relatively new to Elixir world. Currently I’m working on a GraphQL API with Absinthe. All is going right, I have done some logic, some tests to the business logic layer, etc.
Now I’m trying to test my web layer (resolvers), but every time I’m stuck getting this response every time I try to make a request from ExUnit.
%{
"errors" => [
%{
"locations" => [%{"column" => 1, "line" => 1}],
"message" => "Parsing failed at `--plug_con`"
}
]
}
The app works just fine from Postman, here it’s my test file
defmodule Test.Web.Resolver.Session do
alias Mix.Tasks.Phx.Routes
use Test.Setup.ConnCase, async: true
@login_mutation """
query GetUser($id: ID!){
user(id: $id) {
id,
email,
firstName,
posts {
id,
title
}
}
}
"""
setup %{conn: conn} do
:ok
end
test "prueba", %{conn: conn} do
conn =
post(conn, "/api/graphql", %{
"mutation" => @login_mutation,
"variables" => %{id: 1}
})
IO.inspect(conn)
IO.inspect(json_response(conn, 200))
end
end
Any idea why is this happening?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
benwilson512
Hi @crisdegraciadev welcome! That is a very strange error, I’ve never seen it before.
There are definitely a few things that are strange about your test though.
@login_mutationthat is a graphql query, not a mutation. It also doesn’t look like it does a login"mutation"key for the document, but the document key in the POST body should always be"query"whether it’s a mutation doc or otherwiseAre you able to put your code up somewhere that I can see this happen?
crisdegraciadev
Nvm, I though that If it was a mutation I should call it mutation instead of query
.
About the mess with
@login_mutation, I was testing some things, but now i’t solved as working.Thanks!
dimitarvp
It helps future readers if you show how you solved it.
crisdegraciadev
I did it
paulstatezny
I just ran into this as well.
Just to clarify, the problem here was @benwilson512 's (2):
So this:
Should have been this: