Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Formulate testing strategy for GraphQL code #216

Open
pheuberger opened this issue Jan 21, 2025 · 0 comments
Open

Formulate testing strategy for GraphQL code #216

pheuberger opened this issue Jan 21, 2025 · 0 comments
Assignees
@Jipperism @pheuberger @bitbeckers
Labels
enhancement New feature or request

Comments

@pheuberger
Copy link
Member

pheuberger commented Jan 21, 2025 •
edited
Loading

Right now we have to disable code coverage for all files under graphql/ because we don't have a strategy on how to test it. See

hypercerts-api/vitest.config.ts

Line 25 in 32c6505

"src/graphql/**/*",

The files SupabaseCachingService.ts and SupabaseDataService.ts also tend to grow any time we touch something GraphQL related. They are currently included in code coverage reports and make it difficult for you to not dip below thresholds if a PR was only about adding support for a new GraphQL entity.
@pheuberger pheuberger added the enhancement New feature or request label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Jipperism Jipperism

@pheuberger pheuberger

@bitbeckers bitbeckers

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Jipperism @pheuberger @bitbeckers