[bug]: Keploy server throws error when clicked on cross button of the test runs #359
Closed
1 task done
Labels
bug
Something isn't working
Good First Issue
Good for newcomers
Hacktoberfest
HACKTOBERFEST2022
Repo/@ui
Issue Related to Keploy UI Repository
Is there an existing issue for this?
Current behavior
I am using latest image for the keploy UI and when I click on the cross button it is showing following stacktrace -
keploy_1 | 2022-10-03T09:47:36.199Z ERROR regression/regression.go:116 failed to get testcases from the DB {"cid": "default_company", "appID": "", "error": "mongo: no documents in result"} keploy_1 | go.keploy.io/server/pkg/service/regression.(*Regression).Get keploy_1 | /app/pkg/service/regression/regression.go:116 keploy_1 | go.keploy.io/server/graph.(*queryResolver).TestCase keploy_1 | /app/graph/schema.resolvers.go:149 keploy_1 | go.keploy.io/server/graph/generated.(*executionContext)._Query_testCase.func2 keploy_1 | /app/graph/generated/generated.go:2959 keploy_1 | github.com/99designs/gqlgen/graphql/executor.processExtensions.func4 keploy_1 | /go/pkg/mod/github.com/99designs/gqlgen@v0.15.1/graphql/executor/extensions.go:72 keploy_1 | go.keploy.io/server/graph/generated.(*executionContext)._Query_testCase keploy_1 | /app/graph/generated/generated.go:2957 keploy_1 | go.keploy.io/server/graph/generated.(*executionContext)._Query.func7 keploy_1 | /app/graph/generated/generated.go:6507 keploy_1 | github.com/99designs/gqlgen/graphql/executor.processExtensions.func3 keploy_1 | /go/pkg/mod/github.com/99designs/gqlgen@v0.15.1/graphql/executor/extensions.go:69 keploy_1 | go.keploy.io/server/graph/generated.(*executionContext)._Query.func8 keploy_1 | /app/graph/generated/generated.go:6512 keploy_1 | go.keploy.io/server/graph/generated.(*executionContext)._Query.func9 keploy_1 | /app/graph/generated/generated.go:6516
Steps to reproduce
PS - You will see the above error caused due to execution of query for getting testcase which is unnecessary .
Environment
No response
Version
Local
The text was updated successfully, but these errors were encountered: