olzstocks.blogg.se

The source code is available on GitHub. We also provide NuGet packages which contain a series of useful steps and transformations: We've released it as a NuGet Package and is available by using the following command: The example below shows how simple it is to use: Mike Larah wrote a neat little extension for SpecFlow that allows you to specify a tag against your scenario and this will seek out the Storage Emulator and invoke it, if it's not already running. So it makes more sense to try and make your spec run against the emulator. One exception is if you've hosted your code in a public repo in this case you really don't want to commit your real Azure Storage connection details into that repo to allow your integration tests to run on your build server. In most cases, when writing an integration specifications against Azure Storage, you want to use the real thing rather than the Storage Emulator as the performance profile and behaviours are noticeably different. By Howard van Rooijen Co-Founder 15th April 2015