Discussion:
[specflow] SpecFlow v2 plans and git repo changes
Gáspár Nagy
2015-01-22 11:41:45 UTC
Permalink
Hi,

As discussed with some of you, especially with Darren, I have started to
work on SpecFlow v2. As the version number change shows, this will be a
structural change, with the primary goal of:

- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier to
setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests

Now the first steps are done:

1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github repo:
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible

Next steps:
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)

Open questions:
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?

If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.

Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dirk Rombauts
2015-01-23 08:33:22 UTC
Permalink
Hi Gáspár,

Great to read that SpecFlow v2 is receiving some attention :-)

Regarding the question on how to configure a CI build: I recommend you take
a look at http://www.appveyor.com/ - it's dead easy to setup a CI build
there, there's a good many configuration options, good documentation and
good support. It's free for open source projects (I'm using it for
Pickles). The free tier is not too fast, but they have a premium plan with
"Super-fast build environment" and they offer a 50% discount on that for
open source projects - maybe you can find a company willing to sponsor that
;-)

As I said, I'm using it for Pickles, and I'd be happy to assist you in
setting up a CI build for SpecFlow.

Dirk
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started to
work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier to
setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gáspár Nagy
2015-01-28 15:17:18 UTC
Permalink
Hi,

Sounds good. It would be very good if you would help with setting it up.
Let me know what you need for that.

Br,
Gaspar
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started to
work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier to
setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dirk Rombauts
2015-01-29 09:25:01 UTC
Permalink
Hi,

So ... I forked SpecFlow and configured an AppVeyor build. It's building
now but the tests fail. Still: it builds :-)

The next step is for you to go to appveyor.com, sign in with your Github
credentials and add the SpecFlow project. You will need to do a few tweaks
to the build settings.

First, in the general tab of settings:

<Loading Image...>


- Set the Default branch to v2,
- indicate that Only Branches below - v2 should be built.


Then, in the Build tab of the settings:

<Loading Image...>

- Enter the name of the solution to be built.
- Activate the "CMD" option for "Before build script" and enter the
"nuget restore" snippet.

It goes without saying that you should save those settings in each tab ;-)

Trigger a new build and after some queuing time and about 10 minutes of
build time you will have a failed build because of failing tests.

If you need more info: just ask, either here or directly (you know where I
live ;-) ).

br,
Dirk
Post by Gáspár Nagy
Hi,
Sounds good. It would be very good if you would help with setting it up.
Let me know what you need for that.
Br,
Gaspar
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started to
work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier
to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-02-14 08:25:15 UTC
Permalink
Hi,

I'm also very happy that this is receiving some attention. I'm keen to help
out getting a v2 release finished. I have submitted a couple of small pull
requests to specflow in the last few months, but had some problems getting
it to build on my machine. I'll try and get the latest branch pulled and
building locally so I can start to help out. I'm also happy to help out
getting the project building on a CI server.How are tasks managed to make
sure we don't have people stepping on each others toes work wise? Are there
anymore details on the next steps, so I can get started with something?

Cheers,

Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started to
work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier to
setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gáspár Nagy
2015-02-23 09:03:13 UTC
Permalink
Hi,

Coordination: let's try to do it here... Not ideal, but that's what we have.

Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.

Regarding the upcoming tasks, that I think you (or others can pick):
1. Upgrade "generateall" command to support new MsBuild infrastructure: if
you compile the project now, there is a warning. Based on that the new
infrastructure can be researched and used. This is more an infrastructural
task.
2. Implement priorities for the different hooks (e.g. [BeforeScenario]).
Here the syntax/behavior should be similar to the Cucumber JVM counterpart:
http://cucumber.github.io/api/cucumber/jvm/javadoc/cucumber/api/java/Before.html.
This is more of an implementation task.

If you pick any of these (or further ones), just post here first, so that
we know you working on it. In any case (especially the 2) the first should
be to write the tests.

Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen to
help out getting a v2 release finished. I have submitted a couple of small
pull requests to specflow in the last few months, but had some problems
getting it to build on my machine. I'll try and get the latest branch
pulled and building locally so I can start to help out. I'm also happy to
help out getting the project building on a CI server.How are tasks managed
to make sure we don't have people stepping on each others toes work wise?
Are there anymore details on the next steps, so I can get started with
something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started to
work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier
to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-02-23 11:08:38 UTC
Permalink
I have checked out the v2 branch and been able to build successfully. I see
the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild infrastructure: if
you compile the project now, there is a warning. Based on that the new
infrastructure can be researched and used. This is more an infrastructural
task.
2. Implement priorities for the different hooks (e.g. [BeforeScenario]).
http://cucumber.github.io/api/cucumber/jvm/javadoc/cucumber/api/java/Before.html.
This is more of an implementation task.
If you pick any of these (or further ones), just post here first, so that
we know you working on it. In any case (especially the 2) the first should
be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen to
help out getting a v2 release finished. I have submitted a couple of small
pull requests to specflow in the last few months, but had some problems
getting it to build on my machine. I'll try and get the latest branch
pulled and building locally so I can start to help out. I'm also happy to
help out getting the project building on a CI server.How are tasks managed
to make sure we don't have people stepping on each others toes work wise?
Are there anymore details on the next steps, so I can get started with
something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started to
work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier
to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gáspár Nagy
2015-02-23 15:37:06 UTC
Permalink
Yes. here is the best.

BTW: i have moved the build to its final location:
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully. I
see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
if you compile the project now, there is a warning. Based on that the new
infrastructure can be researched and used. This is more an infrastructural
task.
2. Implement priorities for the different hooks (e.g. [BeforeScenario]).
http://cucumber.github.io/api/cucumber/jvm/javadoc/cucumber/api/java/Before.html.
This is more of an implementation task.
If you pick any of these (or further ones), just post here first, so that
we know you working on it. In any case (especially the 2) the first should
be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen to
help out getting a v2 release finished. I have submitted a couple of small
pull requests to specflow in the last few months, but had some problems
getting it to build on my machine. I'll try and get the latest branch
pulled and building locally so I can start to help out. I'm also happy to
help out getting the project building on a CI server.How are tasks managed
to make sure we don't have people stepping on each others toes work wise?
Are there anymore details on the next steps, so I can get started with
something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started
to work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and easier
to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes, monodevelop,
sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the pending
tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google Groups
"SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-03-12 22:41:14 UTC
Permalink
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully. I
see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
if you compile the project now, there is a warning. Based on that the new
infrastructure can be researched and used. This is more an infrastructural
task.
2. Implement priorities for the different hooks (e.g. [BeforeScenario]).
http://cucumber.github.io/api/cucumber/jvm/javadoc/cucumber/api/java/Before.html.
This is more of an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen to
help out getting a v2 release finished. I have submitted a couple of small
pull requests to specflow in the last few months, but had some problems
getting it to build on my machine. I'll try and get the latest branch
pulled and building locally so I can start to help out. I'm also happy to
help out getting the project building on a CI server.How are tasks managed
to make sure we don't have people stepping on each others toes work wise?
Are there anymore details on the next steps, so I can get started with
something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started
to work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-03-16 20:13:31 UTC
Permalink
I'll take on the 2nd task as well, the implementation of priorities for the
different hooks.

I'm assuming that basically what is wanted is the ability to specify and
Order value in a hook and that Specflow will ensure that hooks with lower
orders are always executed first?

I'll try and get this started in the next week or so.

Any pointers as to where in the code the hooks are collected and executed
is appreciated.

Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully. I
see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
if you compile the project now, there is a warning. Based on that the new
infrastructure can be researched and used. This is more an infrastructural
task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more of an
implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen to
help out getting a v2 release finished. I have submitted a couple of small
pull requests to specflow in the last few months, but had some problems
getting it to build on my machine. I'll try and get the latest branch
pulled and building locally so I can start to help out. I'm also happy to
help out getting the project building on a CI server.How are tasks managed
to make sure we don't have people stepping on each others toes work wise?
Are there anymore details on the next steps, so I can get started with
something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started
to work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gáspár Nagy
2015-03-17 07:33:42 UTC
Permalink
Yes. Please go ahead. I would like to review the pending FRs on the master,
and let you what we should do with them.

Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.

Thanks a lot!

Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities for
the different hooks.
I'm assuming that basically what is wanted is the ability to specify and
Order value in a hook and that Specflow will ensure that hooks with lower
orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and executed
is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully. I
see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more of
an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen
to help out getting a v2 release finished. I have submitted a couple of
small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gáspár Nagy
2015-03-17 12:39:45 UTC
Permalink
Tracking update: I have created a Wiki page to provide an overview what is
left for v2.

We should still keep the discussions here though.

https://github.com/techtalk/SpecFlow/wiki/v2-TODO

Br,
Gaspar
Post by Gáspár Nagy
Yes. Please go ahead. I would like to review the pending FRs on the
master, and let you what we should do with them.
Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.
Thanks a lot!
Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities for
the different hooks.
I'm assuming that basically what is wanted is the ability to specify and
Order value in a hook and that Specflow will ensure that hooks with lower
orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and executed
is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully.
I see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more of
an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen
to help out getting a v2 release finished. I have submitted a couple of
small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild
infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Umair Chagani
2015-03-19 17:30:51 UTC
Permalink
Are there any plans to use ExpandoObject
<https://msdn.microsoft.com/en-us/library/system.dynamic.expandoobject%28v=vs.110%29.aspx>
for
retrieving scenario/feature context values?

So instead of doing:

ScenarioContext.Current.Add("somekey", myObject)

var mySavedObject = ScenarioContext.Current["somekey"] as MyObject


This would be more intuitive:


ScenarioContext.Current.SomeKey = myObject

var mySavedObject = ScenarioContext.Current.SomeKey
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gáspár Nagy
2015-03-24 06:10:14 UTC
Permalink
Good idea in general, but ScenarioConetxt.Current also have "fixed"
properties currently, like ScenarioContext.Current.Error. This way they
would be mixed with the state bag values.
Post by Umair Chagani
Are there any plans to use ExpandoObject
<https://msdn.microsoft.com/en-us/library/system.dynamic.expandoobject%28v=vs.110%29.aspx> for
retrieving scenario/feature context values?
ScenarioContext.Current.Add("somekey", myObject)
var mySavedObject = ScenarioContext.Current["somekey"] as MyObject
ScenarioContext.Current.SomeKey = myObject
var mySavedObject = ScenarioContext.Current.SomeKey
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-03-27 08:37:17 UTC
Permalink
I've updated the page with latest changes and assigned myself to the
Cleanup nuget package generation task. I'll also try and get the nuget
package (and visx) as artifacts of the build during this task.

It would help if I could get a bit more detail on what the actual goal is.
Presumably we still want the build to generate a nuget package? Do we just
want this to be in the Debug\Bin\ folder of the relevant project rather
than in the SpecFlowBinPackage?

Anyway its likely a couple of days before I can look at it in anger so if I
don't hear anything before then I'll try and come back with more concrete
questions.
Post by Gáspár Nagy
Tracking update: I have created a Wiki page to provide an overview what is
left for v2.
We should still keep the discussions here though.
https://github.com/techtalk/SpecFlow/wiki/v2-TODO
Br,
Gaspar
Post by Gáspár Nagy
Yes. Please go ahead. I would like to review the pending FRs on the
master, and let you what we should do with them.
Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.
Thanks a lot!
Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities for
the different hooks.
I'm assuming that basically what is wanted is the ability to specify and
Order value in a hook and that Specflow will ensure that hooks with lower
orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and
executed is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully.
I see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more of
an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen
to help out getting a v2 release finished. I have submitted a couple of
small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild
infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "SpecFlow" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/specflow/hMfkAr4uLoA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gáspár Nagy
2015-03-27 15:11:08 UTC
Permalink
I have some ideas how the package generation could work. I'll try to
summarize it on Monday. Please hold on.
Post by Sam Holder
I've updated the page with latest changes and assigned myself to the
Cleanup nuget package generation task. I'll also try and get the nuget
package (and visx) as artifacts of the build during this task.
It would help if I could get a bit more detail on what the actual goal is.
Presumably we still want the build to generate a nuget package? Do we just
want this to be in the Debug\Bin\ folder of the relevant project rather
than in the SpecFlowBinPackage?
Anyway its likely a couple of days before I can look at it in anger so if
I don't hear anything before then I'll try and come back with more concrete
questions.
Post by Gáspár Nagy
Tracking update: I have created a Wiki page to provide an overview what
is left for v2.
We should still keep the discussions here though.
https://github.com/techtalk/SpecFlow/wiki/v2-TODO
Br,
Gaspar
Post by Gáspár Nagy
Yes. Please go ahead. I would like to review the pending FRs on the
master, and let you what we should do with them.
Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.
Thanks a lot!
Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities for
the different hooks.
I'm assuming that basically what is wanted is the ability to specify
and Order value in a hook and that Specflow will ensure that hooks with
lower orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and
executed is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build
successfully. I see the warning indicated in task 1 and so am happy to pick
that up and research how to replace the current obsolete usage with the new
methods. If I have any questions about how the current feature works where
is the best place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more
of an implementation task.
If you pick any of these (or further ones), just post here first,
so that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm
keen to help out getting a v2 release finished. I have submitted a couple
of small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone,
Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "SpecFlow" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/specflow/hMfkAr4uLoA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-03-27 16:08:48 UTC
Permalink
Ok I'll have a look at it over the weekend and try and form some opinions
as well. :)
Post by Gáspár Nagy
I have some ideas how the package generation could work. I'll try to
summarize it on Monday. Please hold on.
Post by Sam Holder
I've updated the page with latest changes and assigned myself to the
Cleanup nuget package generation task. I'll also try and get the nuget
package (and visx) as artifacts of the build during this task.
It would help if I could get a bit more detail on what the actual goal
is. Presumably we still want the build to generate a nuget package? Do we
just want this to be in the Debug\Bin\ folder of the relevant project
rather than in the SpecFlowBinPackage?
Anyway its likely a couple of days before I can look at it in anger so if
I don't hear anything before then I'll try and come back with more concrete
questions.
Post by Gáspár Nagy
Tracking update: I have created a Wiki page to provide an overview what
is left for v2.
We should still keep the discussions here though.
https://github.com/techtalk/SpecFlow/wiki/v2-TODO
Br,
Gaspar
Post by Gáspár Nagy
Yes. Please go ahead. I would like to review the pending FRs on the
master, and let you what we should do with them.
Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.
Thanks a lot!
Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities
for the different hooks.
I'm assuming that basically what is wanted is the ability to specify
and Order value in a hook and that Specflow will ensure that hooks with
lower orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and
executed is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete
MSBuild stuff. Sorry it took so long, life seemed to get in the way. What
would be useful next? I have two pull requests for a different branch,
should I start by submitting those as pull requests for the new v2 branch?
There are other pull requests which will probably need porting over as
well. Should I start trying to merge those with the v2 branch? When might
we be able to get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build
successfully. I see the warning indicated in task 1 and so am happy to pick
that up and research how to replace the current obsolete usage with the new
methods. If I have any questions about how the current feature works where
is the best place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's
what we have.
Build: With Dirk we were able to setup a build. That works
~stable. Currently it works under my personal account unfortunately, so I
yet have to relocate it to a general "specflow" account. I'll keep you
posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more
of an implementation task.
If you pick any of these (or further ones), just post here first,
so that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm
keen to help out getting a v2 release finished. I have submitted a couple
of small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone,
Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "SpecFlow" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/specflow/hMfkAr4uLoA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "SpecFlow" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/specflow/hMfkAr4uLoA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-03-24 21:48:30 UTC
Permalink
Ok I'm almost done with this task but have a couple of questions about how
the feature should work.

1. in the cucumber JVM it seems that for Before* hooks the methods with
lower order values are run first and in the After* hooks the numbers with
the higher values are run first. This doesn't seem logical to me and I
wonder if this is how it should be implemented, or if we should always run
the lower (or higher) numbers first?
2. the java version talks about order but the original post here talked
about priority. Priority feels like a better fit for me (and then we could
always execute higher priorities first). Do we want the attribute to
contain an order value or a priority value?

thanks!

Sam
Post by Gáspár Nagy
Yes. Please go ahead. I would like to review the pending FRs on the
master, and let you what we should do with them.
Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.
Thanks a lot!
Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities for
the different hooks.
I'm assuming that basically what is wanted is the ability to specify and
Order value in a hook and that Specflow will ensure that hooks with lower
orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and executed
is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully.
I see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more of
an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen
to help out getting a v2 release finished. I have submitted a couple of
small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild
infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
m***@gmail.com
2015-03-25 16:41:58 UTC
Permalink
Hi all,

I recently started using SpecFlow and as I have a decent experience with VS
Extensibility, I would like to make some suggestions and contribute.
Is there a specific thread for what concerns VS?

Can I just shoot my ideas on how to improve it, eventually build it?

Thanks and keep up the good work!
Post by Sam Holder
Ok I'm almost done with this task but have a couple of questions about how
the feature should work.
1. in the cucumber JVM it seems that for Before* hooks the methods with
lower order values are run first and in the After* hooks the numbers with
the higher values are run first. This doesn't seem logical to me and I
wonder if this is how it should be implemented, or if we should always run
the lower (or higher) numbers first?
2. the java version talks about order but the original post here talked
about priority. Priority feels like a better fit for me (and then we could
always execute higher priorities first). Do we want the attribute to
contain an order value or a priority value?
thanks!
Sam
Post by Gáspár Nagy
Yes. Please go ahead. I would like to review the pending FRs on the
master, and let you what we should do with them.
Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.
Thanks a lot!
Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities for
the different hooks.
I'm assuming that basically what is wanted is the ability to specify and
Order value in a hook and that Specflow will ensure that hooks with lower
orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and
executed is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully.
I see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more of
an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen
to help out getting a v2 release finished. I have submitted a couple of
small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild
infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-03-26 21:53:21 UTC
Permalink
I'd say if you have experience there are a couple of issues with VS that
need looking at. Specifically this one
<https://github.com/techtalk/SpecFlow/issues/357> and this one
<https://github.com/techtalk/SpecFlow/issues/344>need fixing IMHO.

Other than that lets hear the suggestions and take it from there!
Post by m***@gmail.com
Hi all,
I recently started using SpecFlow and as I have a decent experience with
VS Extensibility, I would like to make some suggestions and contribute.
Is there a specific thread for what concerns VS?
Can I just shoot my ideas on how to improve it, eventually build it?
Thanks and keep up the good work!
Post by Sam Holder
Ok I'm almost done with this task but have a couple of questions about
how the feature should work.
1. in the cucumber JVM it seems that for Before* hooks the methods with
lower order values are run first and in the After* hooks the numbers with
the higher values are run first. This doesn't seem logical to me and I
wonder if this is how it should be implemented, or if we should always run
the lower (or higher) numbers first?
2. the java version talks about order but the original post here talked
about priority. Priority feels like a better fit for me (and then we could
always execute higher priorities first). Do we want the attribute to
contain an order value or a priority value?
thanks!
Sam
Post by Gáspár Nagy
Yes. Please go ahead. I would like to review the pending FRs on the
master, and let you what we should do with them.
Regarding the ordering: the behavior should be as close as possible to
Cucumber JVM (the interesting is what is the default priority, etc). I had
a link to the docs in my previous post. You can also look into the
CucumberJVM source if necessary.
Thanks a lot!
Br,
Gaspar
Post by Sam Holder
I'll take on the 2nd task as well, the implementation of priorities for
the different hooks.
I'm assuming that basically what is wanted is the ability to specify
and Order value in a hook and that Specflow will ensure that hooks with
lower orders are always executed first?
I'll try and get this started in the next week or so.
Any pointers as to where in the code the hooks are collected and
executed is appreciated.
Sam
Post by Sam Holder
Ok I have submitted a pull request for the updates to obsolete MSBuild
stuff. Sorry it took so long, life seemed to get in the way. What would be
useful next? I have two pull requests for a different branch, should I
start by submitting those as pull requests for the new v2 branch? There are
other pull requests which will probably need porting over as well. Should I
start trying to merge those with the v2 branch? When might we be able to
get a v2 build so we can start dogfooding this?
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build
successfully. I see the warning indicated in task 1 and so am happy to pick
that up and research how to replace the current obsolete usage with the new
methods. If I have any questions about how the current feature works where
is the best place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
1. Upgrade "generateall" command to support new MsBuild
infrastructure: if you compile the project now, there is a warning. Based
on that the new infrastructure can be researched and used. This is more an
infrastructural task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
Cucumber JVM counterpart: http://cucumber.github.io/api/
cucumber/jvm/javadoc/cucumber/api/java/Before.html. This is more
of an implementation task.
If you pick any of these (or further ones), just post here first,
so that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm
keen to help out getting a v2 release finished. I have submitted a couple
of small pull requests to specflow in the last few months, but had some
problems getting it to build on my machine. I'll try and get the latest
branch pulled and building locally so I can start to help out. I'm also
happy to help out getting the project building on a CI server.How are tasks
managed to make sure we don't have people stepping on each others toes work
wise? Are there anymore details on the next steps, so I can get started
with something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have
started to work on SpecFlow v2. As the version number change shows, this
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
3. Removed VS2013 integration and moved it to a separate github
repo: https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the
master branch?
- How do we support alternative runtimes (Win8.1, WinPhone,
Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-04-01 15:48:44 UTC
Permalink
I have configured Appveyor to publish the nuget packages in the project
feed, but currently it only uses the fixed version defined in the nuspec
file. Presumably it would be better if we could include the current build
number in the version of the package. I'll look at adding a powershell
script to do that unless anyone thinks thats a bad idea?

Cheers

Sam
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully. I
see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
if you compile the project now, there is a warning. Based on that the new
infrastructure can be researched and used. This is more an infrastructural
task.
2. Implement priorities for the different hooks (e.g. [BeforeScenario]).
http://cucumber.github.io/api/cucumber/jvm/javadoc/cucumber/api/java/Before.html.
This is more of an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen to
help out getting a v2 release finished. I have submitted a couple of small
pull requests to specflow in the last few months, but had some problems
getting it to build on my machine. I'll try and get the latest branch
pulled and building locally so I can start to help out. I'm also happy to
help out getting the project building on a CI server.How are tasks managed
to make sure we don't have people stepping on each others toes work wise?
Are there anymore details on the next steps, so I can get started with
something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started
to work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sam Holder
2015-04-02 07:16:19 UTC
Permalink
Ok the Appveyor project nuget feed publishes the nuget packages created
during the build, and the version number of the package reflects the build
number of the build. I have only updated the versions of the Specflow
package and the Specflow.CustomPlugin package. The nunit/xunit/nunitrunners
[packages have the default versions still. What do we want to do with the
version number for these? These are only available on the project feed on
appveyor but I'm not sure if that URL is publicly published or not.

Once pull request #425 <https://github.com/techtalk/SpecFlow/pull/425> is
merged then we will start dogfooding at work I think (as then we have the
same functionality we currently have), at least in my team.
Post by Sam Holder
I have configured Appveyor to publish the nuget packages in the project
feed, but currently it only uses the fixed version defined in the nuspec
file. Presumably it would be better if we could include the current build
number in the version of the package. I'll look at adding a powershell
script to do that unless anyone thinks thats a bad idea?
Cheers
Sam
Post by Gáspár Nagy
Yes. here is the best.
https://ci.appveyor.com/project/SpecFlow/specflow
Post by Sam Holder
I have checked out the v2 branch and been able to build successfully. I
see the warning indicated in task 1 and so am happy to pick that up and
research how to replace the current obsolete usage with the new methods. If
I have any questions about how the current feature works where is the best
place to ask them? Here?
Post by Gáspár Nagy
Hi,
Coordination: let's try to do it here... Not ideal, but that's what we have.
Build: With Dirk we were able to setup a build. That works ~stable.
Currently it works under my personal account unfortunately, so I yet have
to relocate it to a general "specflow" account. I'll keep you posted.
if you compile the project now, there is a warning. Based on that the new
infrastructure can be researched and used. This is more an infrastructural
task.
2. Implement priorities for the different hooks (e.g.
[BeforeScenario]). Here the syntax/behavior should be similar to the
http://cucumber.github.io/api/cucumber/jvm/javadoc/cucumber/api/java/Before.html.
This is more of an implementation task.
If you pick any of these (or further ones), just post here first, so
that we know you working on it. In any case (especially the 2) the first
should be to write the tests.
Br,
Gaspar
Post by Sam Holder
Hi,
I'm also very happy that this is receiving some attention. I'm keen to
help out getting a v2 release finished. I have submitted a couple of small
pull requests to specflow in the last few months, but had some problems
getting it to build on my machine. I'll try and get the latest branch
pulled and building locally so I can start to help out. I'm also happy to
help out getting the project building on a CI server.How are tasks managed
to make sure we don't have people stepping on each others toes work wise?
Are there anymore details on the next steps, so I can get started with
something?
Cheers,
Sam
Post by Gáspár Nagy
Hi,
As discussed with some of you, especially with Darren, I have started
to work on SpecFlow v2. As the version number change shows, this will be a
- upgrading to the latest infrastructure (.NET 4.5, VS2013)
- simplifying the code so that people can better contribute (and
easier to setup a CI)
- integrate the new gherkin parser (v3)
- smaller feature requests
1. Created a "v2" branch
2. Removed obsolete/unused projects (alternative runtimes,
monodevelop, sharpdevelop integration, vs2010)
https://github.com/techtalk/SpecFlow.VisualStudio
4. Upgraded all projects to .NET 4.5 and VS2013
5. Replaced lib references with NuGet wherever it was possible
- Upgrade "generateall" command to support new MsBuild infrastructure
- Remove SpecFlow.Reporting from the main repo
- Cleanup NuGet package generation (eliminate SpecFlowBinPackage)
- How to apply the pending pull requests that were sent to the master
branch?
- How do we support alternative runtimes (Win8.1, WinPhone, Xamarin, etc.)?
- How shall we configure a CI build?
If you have any feedback or willing to contribute in any of the
pending tasks, please let me/us know.
Br,
Gaspar
--
You received this message because you are subscribed to the Google
Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "SpecFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specflow+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...