The ALM Rangers have completed the project “kick-off” meeting this morning, to address the Add "Create Unit Tests" menu option back idea on UserVoice as mentioned in the recent ALM Rangers Triage #3 - What happened to your idea in UserVoice report.
Codename Raven … symbolizing knowledge, creation … the bringer of light.
picture of a Raven on a card in my office, created by Richard Shorty from Yukon.
Phenomenal Core Team
We have a phenomenal core team that are kicking-off the project and will introduce the contributors and testers at a later stage when the “kick-off dust” has settled. If you are wondering about the roles and responsibilities, download our latest Ruck Guide.
|Ruck Master||Brian Blackman||Dev Lead||Rob Jarratt|
|Product Owner||Joshua Weber||Project Lead||Willy-Peter Schaub|
Our current vision, which may change over next few days as we are refining our Epics, is penciled down as:
Add a Create Unit Tests feature back to Visual Studio 2012. Concentrate on automating project creation, adding references and generating stubs, but not on the body of the test methods. Allow multiple test frameworks to be targeted.
Random Quick-Polls … do you agree?
During the kick-off we made four random quick polls. Do you agree with the results?
How important is this unit test code generation feature to you?
What are your expectations for the generated test methods in v1?
Which code generation should this test code generation feature support in v1?
Who are the typical users of this unit test code generation feature?
We would appreciate your candid feedback for the team! Just add a comment to this post or contact me direct.