Permalink
Browse files

We're ready to start testing end-to-end now that we have all the inte…

…rnal pieces in place. Therefore, we created our AcceptanceTests project and added SpecFlow to facilitate that process.
  • Loading branch information...
dragan committed Aug 21, 2010
1 parent d6844fa commit ebf9e6c6a7ba14c719dd9ba48bc58ec019703fd4
@@ -0,0 +1,14 @@
+using System.Reflection;
+using System.Runtime.CompilerServices;
+
+[assembly: AssemblyTitle("SineSignal.Ottoman.AcceptanceSpecs")]
+[assembly: AssemblyDescription("")]
+[assembly: AssemblyConfiguration("")]
+[assembly: AssemblyCompany("")]
+[assembly: AssemblyProduct("SineSignal.Ottoman.AcceptanceSpecs")]
+[assembly: AssemblyCopyright("Copyright © 2010 SineSignal, LLC")]
+[assembly: AssemblyTrademark("")]
+[assembly: AssemblyCulture("")]
+
+[assembly: AssemblyVersion("0.0.0.0")]
+[assembly: AssemblyFileVersion("0.0.0.0")]
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="utf-8"?>
+<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
+ <PropertyGroup>
+ <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
+ <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
+ <ProductVersion>10.0.0</ProductVersion>
+ <SchemaVersion>2.0</SchemaVersion>
+ <ProjectGuid>{1BB84B40-3BA5-4AD0-8690-9851DDE36EC5}</ProjectGuid>
+ <OutputType>Library</OutputType>
+ <RootNamespace>SineSignal.Ottoman.AcceptanceSpecs</RootNamespace>
+ <AssemblyName>SineSignal.Ottoman.AcceptanceSpecs</AssemblyName>
+ <TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
+ </PropertyGroup>
+ <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
+ <DebugSymbols>true</DebugSymbols>
+ <DebugType>full</DebugType>
+ <Optimize>false</Optimize>
+ <OutputPath>bin\Debug</OutputPath>
+ <DefineConstants>DEBUG</DefineConstants>
+ <ErrorReport>prompt</ErrorReport>
+ <WarningLevel>4</WarningLevel>
+ <ConsolePause>false</ConsolePause>
+ </PropertyGroup>
+ <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
+ <DebugType>none</DebugType>
+ <Optimize>false</Optimize>
+ <OutputPath>bin\Release</OutputPath>
+ <ErrorReport>prompt</ErrorReport>
+ <WarningLevel>4</WarningLevel>
+ <ConsolePause>false</ConsolePause>
+ </PropertyGroup>
+ <ItemGroup>
+ <Reference Include="System" />
+ <Reference Include="System.Core" />
+ <Reference Include="nunit.framework, Version=2.4.8.0, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77">
+ <SpecificVersion>False</SpecificVersion>
+ <HintPath>..\..\tools\nunit\nunit.framework.dll</HintPath>
+ </Reference>
+ <Reference Include="TechTalk.SpecFlow, Version=1.3.5.2, Culture=neutral, PublicKeyToken=0778194805d6db41">
+ <SpecificVersion>False</SpecificVersion>
+ <HintPath>..\..\tools\specflow\TechTalk.SpecFlow.dll</HintPath>
+ </Reference>
+ </ItemGroup>
+ <ItemGroup>
+ <Compile Include="AssemblyInfo.cs" />
+ </ItemGroup>
+ <Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
+ <ItemGroup>
+ <ProjectReference Include="..\SineSignal.Ottoman\SineSignal.Ottoman.csproj">
+ <Project>{DFB82EC8-2D77-461A-92D6-B4024E8812FA}</Project>
+ <Name>SineSignal.Ottoman</Name>
+ </ProjectReference>
+ </ItemGroup>
+</Project>
@@ -5,12 +5,18 @@ Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SineSignal.Ottoman.Specs",
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SineSignal.Ottoman", "SineSignal.Ottoman\SineSignal.Ottoman.csproj", "{DFB82EC8-2D77-461A-92D6-B4024E8812FA}"
EndProject
+Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SineSignal.Ottoman.AcceptanceSpecs", "SineSignal.Ottoman.AcceptanceSpecs\SineSignal.Ottoman.AcceptanceSpecs.csproj", "{1BB84B40-3BA5-4AD0-8690-9851DDE36EC5}"
+EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Release|Any CPU = Release|Any CPU
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
+ {1BB84B40-3BA5-4AD0-8690-9851DDE36EC5}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+ {1BB84B40-3BA5-4AD0-8690-9851DDE36EC5}.Debug|Any CPU.Build.0 = Debug|Any CPU
+ {1BB84B40-3BA5-4AD0-8690-9851DDE36EC5}.Release|Any CPU.ActiveCfg = Release|Any CPU
+ {1BB84B40-3BA5-4AD0-8690-9851DDE36EC5}.Release|Any CPU.Build.0 = Release|Any CPU
{34BD81C0-3B86-47C5-9D31-1C35E6CABC6A}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{34BD81C0-3B86-47C5-9D31-1C35E6CABC6A}.Debug|Any CPU.Build.0 = Debug|Any CPU
{34BD81C0-3B86-47C5-9D31-1C35E6CABC6A}.Release|Any CPU.ActiveCfg = Release|Any CPU
View
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
View
@@ -0,0 +1,28 @@
+Copyright (c) 2009, TechTalk
+Disclaimer:
+* The initial codebase of Specflow was written by TechTalk employees.
+ No 3rd party code was included.
+* No code of customer projects was used to create this project.
+* TechTalk had the full rights to publish the initial codebase.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+ * Redistributions of source code must retain the above copyright
+ notice, this list of conditions and the following disclaimer.
+ * Redistributions in binary form must reproduce the above copyright
+ notice, this list of conditions and the following disclaimer in the
+ documentation and/or other materials provided with the distribution.
+ * Neither the name of the SpecFlow project nor the
+ names of its contributors may be used to endorse or promote products
+ derived from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED ''AS IS'' AND ANY
+EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL TECHTALK OR CONTRIBUTORS BE LIABLE FOR ANY
+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@@ -0,0 +1,147 @@
+1.3.5.2 - 2010/08/11
++ Sorry, we're ironing out our deploy strategy with the new Mono/MonoDevelop integration. We didn't
+ change the version in the MonoDevelop Add-In XML file.
+
+1.3.5.1 - 2010/08/11
+
+New features:
++ Support for hosting add-in on http://addins.monodevelop.com
+
+1.3.5 - 2010/08/11
+
+New features:
++ Support for Mono (v2.6.7) & MonoDevelop (v2.4) by Dale Ragan
+
+Fixed issues:
++ Generating code randomly for the wrong testing engine
++ Test class generation problem for Russian feature files
++ Fix tag support for Silverlight
+
+1.3.4 - 2010/07/28
+
+Fixed issues:
++ Installation fails if Visual Studio 2010 is not installed
++ VS2010: Background section is not colored properly
+
+1.3.3 - 2010/07/19
+
+New features:
++ Support for MsTest report generation
+ usage: specflow mstestexecutionreport projectFile [/testResult:value] [/xsltFile:value] [/out:value]
+ projectFile Visual Studio Project File containing specs
+ [/testResult:value] Test Result file generated by MsTest. Defaults to TestResult.trx
+ [/out:value] Generated Output File. Defaults to TestResult.html
+ [/xsltFile:value] Xslt file to use, defaults to built-in stylesheet if not provided
++ Visual Studio 2010 editor support:
+ - syntax coloring with configurable colors ("Gherkin ...")
+ - outlining for scenarios
+ Uninstall the beta integration (TechTalk.SpecFlow.VsIntegration.GherkinFile.vsix) before installing
+ SpecFlow 1.3.3.
+
+Fixed issues:
++ MbUnit execution fails for pending steps (Assert method not found: Inconclusive)
+
+1.3.2 - 2010/06/29
+
+New features:
++ Support for MsTest for .NET 4.0 categories. Configure the test provider name to
+ "MsTest.2010" in order to use the [TestCategory] attribute.
++ Silverlight support (beta), see http://wiki.github.com/techtalk/SpecFlow/silverlight-support
+
+Fixed issues:
++ Report generation fails if no custom XSLT is provided
+
+
+1.3.1 - 2010/06/21
+
+New features:
++ Using standard Gherkin parser (http://github.com/aslakhellesoy/gherkin) v2.0.1
++ Custom XSLT can be specified for generating reports.
+ See examples in Tests/ReportingTests/CustomXsltTemplate.feature
++ The test error can be accessed through ScenarioContext.Current.TestError
+ (e.g. in an AfterScenario event).
++ [StepTransformation] attribute has been renamed to [StepArgumentTransformation]
+ because this name describe the intention better. Using the old attribute will
+ generate a warning.
++ Support for MbUnit
+
+Fixed issues:
++ NullReference exception when using BeforeTestRun event (Issue 41)
+
+1.3.0 - 2010/05/05
+
+New features:
++ Using standard Gherkin parser (http://github.com/aslakhellesoy/gherkin) v1.0.24
++ Context injection in step definitions. Step definitions can get a context injected with
+ constructor injection. (Issue 30)
+ See examples in Tests/FeatureTests/ContextInjection
++ Using steps in other assemblies. This enables writing steps in VB. (Issue 19)
+ See examples in Tests/FeatureTests/ExternalSteps
++ Steps can be invoked from other steps using step text. See examples in
+ Tests/FeatureTests/CallingStepsFromStepDefinitions
++ Custom step parameter converters can be defined as a binding.
+ See examples in Tests/FeatureTests/StepArgumentTransfomation
++ SpecFlow feature files can be added also to VB.NET projects
++ Support for xUnit
++ Single installer for Visual Studio 2008 and 2010 (Issue 6, 10, 11)
++ Place GeneratedCodeAttribute and 'Designer generated code' region on generated code to
+ avoid having this code parsed by code analysis. (Issue 33)
++ Configuration option to disable all output. (Issue 29)
+ Use the following config to disable output:
+ <trace listener="TechTalk.SpecFlow.Tracing.NullListener, TechTalk.SpecFlow" />
+
+Fixed issues:
++ SpecFlow Reporting doesn't work with Firefox (Issue 31)
++ Binding methods are executed using the culture of the feature file.
++ Several parsing issues are solved now (Issue 1, 8, 9, 37)
+
+1.2.0 - 2009/11/25
+
+New features:
++ Generate #line pragmas to the output file (Issue 26)
++ Allow transformation of feature files from command-line and MsBuild (Issue 3)
++ Merge all command-line tool (generation, reports) to a single executable: specflow.exe
++ Support for Dutch and Swedish language
++ Support enumerations in step binding arguments (Issue 28)
+
+Fixed issues:
++ MsTest does not refresh tests automatically (Issue 25)
++ Fixes in report localization
++ Non-string parameters for bindings are not converted using the feature language (Issue 26)
+
+1.1.0 - 2009/11/11
+
+New features:
++ Support for MsTest (Issue 4)
++ Finalize configuration (Issue 13)
++ Support German, French and Hungarian languages (Issue 5)
++ Add strong-name for specflow assemblies (Issue 2)
++ Allow scenario events to be instance methods (Issue 20)
++ More descriptive name for the scenario outline example tests than XYZ_Variant1 (Issue 18)
++ NUnit SpecFlow test execution report (Issue 23)
++ Step definition usage report (Issue 24)
+
+Fixed issues:
++ Runtime: Remove direct dependency on nunit.framework.dll from the runtime (Issue 12)
++ Runtime: Binding methods with more than 4 parameters cannot be used (Issue 21)
++ Generator: Special language characters (e.g. accented letters) are removed when generating
+ test method names (Issue 22)
+
+1.0.2 - 2009/10/20
+
+New features:
++ Runtime: allow non-static bindings
++ Runtime: support multiple step attributes on a single binding method
+
+Fixed issues:
++ VS: Error message is displayed when you add a SpecFlow project item to your project.
++ Parser: mixed order of Given/When/Then is not supported
++ Runtime: the original phrasing of the keywords (Given/And/But) is not preserved
++ Generator: the generated test class has a "Fixture" suffix
++ Parser: specifying any "given" should be optional
+
+
+1.0.1 - 2009/10/13
+
+Initial publish on http://www.specflow.org
+
View
Binary file not shown.

0 comments on commit ebf9e6c

Please sign in to comment.