Skip to content

Conversation

@jcass77
Copy link
Contributor

@jcass77 jcass77 commented Feb 7, 2017

Remove Stormpath test resources once the tests have run.

tearDown() will now remove API keys, users, and groups as well and prevent the Stormpath web interface dashboard from being polluted with old test resources.

The only way I could track down the API keys were to iterate through all accounts looking for applications with names in the correct flask-stormpath-tests format. This seems a little inefficient, but I couldn't find the API keys in the key list of either the application or account resources directly.

I also switched from the deprecated flask.ext import format to the new flask_stormpath while I was at it.

Fixes #83.

@jcass77
Copy link
Contributor Author

jcass77 commented Feb 7, 2017

...on the test failure: this seems to be related to changes to the document build that was introduced as part of 87e19c4?

@rdegges rdegges merged commit 2c0c68d into stormpath:develop Feb 8, 2017
@rdegges
Copy link
Contributor

rdegges commented Feb 8, 2017

This looks good, thanks! I believe I can replace some of the iteration you're doing with a search request, that will save some requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants