Open rmtuckerphx opened 7 years ago
I don't have a solution to this yet but I think this is caused by the Alexa Skills Kit automatically persisting and retrieving session attributes to DynamoDB. Assuming your application checks and sets some kind of user state when handling a request (e.g. this.attributes['lastfact'] = 2
) this state will still be in place for the next test as the Skills Kit will automatically retrieve it prior to invoking your handler.
Possible solutions I've considered are:
I've not found a clean way to access the DynamoDB table in the test suite to implement any of these solutions yet so any suggestions welcome.
The e2e tests should each be running independently of previous runs but it doesn't appear that is the case.