-
Notifications
You must be signed in to change notification settings - Fork 591
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.
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
chore: add kongintegration test flavor and cover UpdateStrategyInMemory as a reference #4802
Conversation
6bf5b6c
to
5519984
Compare
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4802 +/- ##
=======================================
- Coverage 78.1% 78.0% -0.1%
=======================================
Files 163 163
Lines 18544 18537 -7
=======================================
- Hits 14486 14463 -23
- Misses 3255 3267 +12
- Partials 803 807 +4 ☔ View full report in Codecov by Sentry. |
2ffc16a
to
7abdf74
Compare
Target |
5cf1c23
to
4417c23
Compare
Since the contents of this PR have changed (to introduce a new kind of tests) please change the PR title to reflect this fact. |
2c6dded
to
9635e97
Compare
Co-authored-by: Patryk Małek <patryk.malek@konghq.com>
9635e97
to
a2b85e4
Compare
a2b85e4
to
a3327a2
Compare
What this PR does / why we need it:
Adds an integration test for
sendconfig.UpdateStrategyInMemory
to verify we correctly integrate with Kong's flattened errors.It also creates a separate "kongintegration" test flavor (name to be discussed, I'm open to suggestions). I think we could benefit from having more coverage in this kind of tests instead of always adding a regular integration or E2E case. They all could be independent and run in parallel with no problems. We could test various Kong settings in them as every test spawns its own Kong instance. Their only dependency is to have a running docker daemon.
Which issue this PR fixes:
Follow up of #4790.