In my previous post on BDD, I alluded to tools that would come along to help with bridging the gap between specifications and test code.
"...new advances in DSLs would provide a potential bridge to generate
functional code to validate the requirements have been met. It seems to
me this would provide a much higher value from a testing and code
quality perspective as you are now writing tests that are 1) driven
directly by the requirements; 2) oriented at a piece of functionality
that directly affects the user."
A tweet from @ryanlanciaux today pointed me to SpecFlow. This tool looks to have a lot of promise in doing just what I described above.
You can read more about SpecFlow and download it from here: http://specflow.org/home.aspx
I plan on downloading SpecFlow this week and giving it a look. I'll post more on my experiences and thoughts regarding this tool after had some time with it.
"...new advances in DSLs would provide a potential bridge to generate
functional code to validate the requirements have been met. It seems to
me this would provide a much higher value from a testing and code
quality perspective as you are now writing tests that are 1) driven
directly by the requirements; 2) oriented at a piece of functionality
that directly affects the user."
A tweet from @ryanlanciaux today pointed me to SpecFlow. This tool looks to have a lot of promise in doing just what I described above.
You can read more about SpecFlow and download it from here: http://specflow.org/home.aspx
I plan on downloading SpecFlow this week and giving it a look. I'll post more on my experiences and thoughts regarding this tool after had some time with it.
