chore: fix test warnings across test suite #1468
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1468 +/- ##
=======================================
Coverage 91.31% 91.31%
=======================================
Files 229 229
Lines 7266 7266
=======================================
Hits 6635 6635
Misses 631 631 ☔ View full report in Codecov by Sentry. |
zimeg
left a comment
There was a problem hiding this comment.
@WilliamBergamin Another amazing change in care for this project 🧪 ✨
Please merge when's right but I left a curious question if the answer is quick-
| "ENGINE": "django.db.backends.sqlite3", | ||
| "NAME": "logs/db.sqlite3", | ||
| "NAME": ":memory:", |
There was a problem hiding this comment.
👁️🗨️ question: Does this sqlite implementation not use the file system? I haven't explored these tests much but found this surprising at glance!
There was a problem hiding this comment.
Good point I found another way to silence the django warning 🙏
Summary
This PR aims to fix some warnings that were showing up in our unit tests 🙏
Testing
CI should be sufficient
Category
slack_bolt.Appand/or its core componentsslack_bolt.async_app.AsyncAppand/or its core componentsslack_bolt.adapter/docsRequirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
./scripts/install_all_and_run_tests.shafter making the changes.