Writing unit tests for an app using this SDK

[devangmehta123]

I have seen mentions of unit tests in some issues like this one: #1052

But the documentation does not mention how we can write unit tests in our code if we integrate the slack sdk in our code base.

We use pytest along with moto3 to mock AWS APIs, for example. Is there something similar we can do for this slack sdk or do we have to make our own fixtures to make the unit tests work?

[seratch]

Hi @devangmehta123, thanks for writing in!

At this moment, there is no built-in support for testing your code using this SDK.

As for the unit tests verifying the behavior of this SDK itself spins up a mock HTTP server with fixture data this way: https://github.com/slackapi/python-slack-sdk/tree/v3.15.2/tests/slack_sdk/web If you are fine with this approach, please feel free to reuse the mock server implementation for your tests.

For the future, we are thinking of some better testing support for this low-level SDK and Bolt framework. The moto library is an amazing tool! I like it too. That being said, our forthcoming testing support for this SDK would be a bit simpler. Simulating the whole Slack platform is relatively complex. I cannot tell when the new module will be available yet but I myself already started early prototyping for it.

I'm sorry for providing no clear answer at this moment. I hope this helps!

[devangmehta123]

Thanks @seratch , keep us all posted on the prototype.

I am actually quite happy to use your mock HTTP server for the tests. If that could be made general purpose for unit tests, that could work.

I have seen that approach used for database instances before and the only issue sometimes is the time it takes to start up and tear it down.

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.