I'm putting on a two day training session for a group where some participants might be completely new to unit testing and/or TDD. Almost all are new to TFS. I put together a survey for the participants to gauge my audience. I thought this might be a useful resource for others for looking into training, thinking about training or perhaps even job interview material. Here it is in its raw format directly from the survey engine.
TFS Advantage - Continuous Integration Development with Team Foundation Server 2008
| How much professional programming experience do you have? |
| (Please tick just one of the following boxes) |
- < 1 yr
- 1 - 2 years
- 3 - 5 years
- 6 - 10 years
- Let's swap stories about the price per megabyte of your first hard drive
- This question does not apply to my participation in the sessions.
|
| How much experience (formal or informal) do you have with designing or writing unit tests? |
| (Please tick just one of the following boxes) |
- What's a unit test?
- I've played around with writing a few unit tests in my spare time.
- Some experience on some project somewhere
- I participated in writing a lot of unit tests before in my recent project(s) as part of my daily activities
- It's the first thing I think of before writing production code.
- Some people like to refer to me as Kent Beck, Jr.
- This question does not apply to my participation in the sessions.
|
| Which best describes how you think writing unit tests will impact your software project’s development life cycle? |
| (Please tick just one of the following boxes) |
- Writing unit tests is a waste of time.
- Writing unit tests will ensure our success.
- Writing unit tests is one activity that helps in our development cycle.
- Writing unit tests is something quality assurance (QA) should be doing.
- Writing unit tests is a good idea, but it slows us down too much.
- This question does not apply to my participation in the sessions.
|
| Which answer best describes your experience with continuous integration? |
| (Please tick just one of the following boxes) |
- What's continuous integration?
- Someone else's project used that once, it looked intriguing.
- I worked with it on a project or two in the past.
- My experience has shown me it's a valuable part of the software development life cycle.
- This stuff rocks, I should be the build master!
- This question does not apply to my participation in the sessions.
|
| Which answer best describes the optimal time to write unit tests in your software development process? |
| (Please tick just one of the following boxes) |
- Before you even create the production code.
- When you are having a tough time figuring out how to design a component of your system.
- Before you check in your code.
- When you find a bug in your component.
- Again, isn't this QA's job?
- This question does not apply to my participation in the sessions.
|
| Which answer best describes how many files is a “good” submission to the source code repository participating in a continuous integration process? |
| (Please tick just one of the following boxes) |
- A few files, even if the component is just beginning to take shape.
- No more than ten, otherwise it’s tough to perform a code review.
- You should be completely done with your component before checking in, so as many files as it takes.
- Thirty or fewer, one minute per file in the build, you can't wait longer than that.
- None. With continuous integration, the build server does most of the coding for you.
- This question does not apply to my participation in the sessions.
|
| Which answer best describes your perception of the term “TDD” or “test driven development” or “test driven design”? |
| (Please tick just one of the following boxes) |
- It's another fad in software engineering we will all have a good chuckle about in five years.
- I write some pretty solid code, but this is good stuff for junior developers.
- I'm intrigued, tell me more!
- I think it will help us produce higher quality software.
- I think it could be the only way I approach developing software from here on out.
- Kent Beck, Jr? Some people call me Kent Beck, Sr!
- This question does not apply to my participation in the sessions.
|
| If you have a class (managed .net class, unmanaged C++ class, basic unit of code, etc) in your software’s source code that is 200 lines of code, how many lines of test code would you consider being sufficient or reasonable? |
| (Please tick just one of the following boxes) |
- about 50 lines
- about 50 - 150 lines
- about 150 - 300 lines
- about 300 - 600 lines
- about 600 - 1200 lines
- The more the better, I'm not done writing tests for my first 'hello world' program yet!
- This question does not apply to my participation in the sessions.
|
| What would you like to learn from these sessions? (Feel free to mention specific technologies, methodologies, patterns, etc.) |
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________ |
| What activities do you find the most effective for your learning style in training sessions like these? |
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________ |