Releases · slackapi/steno

11 May 00:12

aoberoi

v1.2.0

afc84d3

v1.2.0 Latest

Latest

Security on the mind

Introducing the --slack-replace-tokens option! Now when you run Steno in record mode with this option enabled, your Slack API tokens will not be saved to scenarios on disk. Instead, Steno will generate a fake token in its place. Each time that happens, the console will show you the real token with the corresponding fake token.

How would I use this? The same workflow applies, you just don't need to hand-edit Slack tokens out of your interactions before committing them to your version control. So now you can just start Steno, use the app normally to record a scenario. Then, when you build the test case, you just use the generated fake tokens instead of fetching them from a real database or API. When you start the scenario in replay mode, Steno will be able to match your interactions with the generated tokens.

One more security feature: Steno used to generate filenames for interactions using the path of a request. We realized that some applications use querystring parameters for sensitive data, so the filenames would contain tokens. That's not ideal, so we changed that behavior. The best part is we were able to make that change without breaking old interaction files.

This release also includes a more helpful guide for using Steno with ngrok in the documentation.

Assets 3

05 Jan 00:49

aoberoi

v1.1.0

317e49f

v1.1.0

Our first release of 2018! 🎉 Here's what we've cooked up for you fine folks:

New CLI options --record and --replay 🎛 -- We've deprecated the previous steno record and steno replay usages, in favor of steno --record and steno --replay. Why? This reflects the point below of our new unified control API implementation. It also paves the way for a future where you can switch modes on the fly without restarting steno. 💯 The previous usage still works, and will continue to work until v2.0.0, but we suggest you make the switch now.
Unified control API 📦 -- You'll notice that if you started steno in record mode, but make a control API request which only functions in replay mode, instead of getting no response at all you'll now get a helpful error response. That should be much less confusing.
Usage statistics 📈 -- We want to make steno the best it can be for you the users. To that end, we've added a prompt that shows when your first run steno so you can decide if we can anonymously collect data about your usage. We won't get any request, response, or scenario information 🔒, only basic counts of lifecycle events. We're open source, so you can see the exact data in this PR.
Specifiying initial scenario 1️⃣ -- You can now use the --scenario-name and --scenario-dir options to specify the initial scenario to record or replay on startup.
Bug fixes 💊 -- Better error messages when the port you want to start steno on is already being used, incoming interaction replay order fixed, matching on empty bodies (as in GET requests) fixed, help output issues fixed.
--version -- steno will output the version number with this option.