Support for accessToken & permissions?

[alopix]

I really like this framework. One feature I'm missing is accessToken (account linking) and permissions. Any plans on adding them?

[hoegertn]

What exactly are you missing here? What do you want the framework to provide?

[hoegertn]

@alopix can you elaborate on your feature request? I will then try to add it.

[alopix]

Sorry for the late reply.

It would be nice to allow to set an accessToken (as well as possibly refreshToken and respective URLs) to allow for testing the Skills with the Alexa account linking features.
Most of my skills are connected via account linking to Google or Alexa OAuth (and even require the user to be logged in to use it). So my Requests would always need the accessToken set beside the userId.

Same with permissions: some of my Skills require the user to allow Device location access which is also a field that does not seem to be supported with this test framework. To include the permissions field in the Request.

[thebucknerlife]

@hoegertn are there any updates on supporting access tokens?

[hoegertn]

How would you like to integration to look like?
I will collect a feature list and dedicate some time to this project in the near future.

[alopix]

It would be nice to have a solution that automatically renews the access token so you don't have to manually take care of entering it all the time.

[hoegertn]

Do you plan to use actual tokens and do real calls in the tests or is the call mocked out and you provide fixed access tokens in your test?

[alopix]

For me it would be more or less for integration tests to ensure that the actual connection between skill lambda and the backend API. Using mock data often results in data fitting the lambda perfectly but an actual backend breaking stuff. 🙈