Refactor all tests with Mock API calls about java-slack-sdk HOT 3 CLOSED

Hi @seratch , I can't believe it's been two years already!

I agree RE maintaining the assets. Although it has a record function (which helps), its very difficult to know which responses may have changed without API versioning.

It might be worth looking at this again if the API becomes versioned and we get a change list on a regular basis.

from java-slack-sdk.

@seratch As discussed, please feel free to assign this to me.

from java-slack-sdk.

Already two years have passed since you posted this issue. 😅 Indeed, using Steno may be fine but I'm still not sure if we can maintain the assets to keep them up-to-date.

Also, this project has a server-side framework, Lightning. It's pretty easy to make sure if an app works as expected by running it like this: https://github.com/seratch/jslack/blob/3.2.0/jslack-lightning/src/test/java/samples/DialogSample.java

I myself don't see any inconvenience so far but I'm open to suggestions from anyone.

from java-slack-sdk.