Add Build section

[jfry]

Given that AREA should be fairly constant, and build numbers often change daily, let's create a build section.

What to do with the data, still TBD.

[aquaman]

Hi Jeff, I now have this section working in the Scan tool based on the conversation we had in email. Not checked in yet. Need a bit more info.

The story so far:

• you can now include a #BUILD section in the CHARTER section at the top of the session sheet.
• you can customise whether or not this section appears via the SBTM.YML config file

Outstanding question: what do we expect the data in this section to look like?

For example, do we expect it to be a one-line identifier of the build?

• Would we expect the Scan tool to throw an error if it encounters multiple lines or build ID's in this section?
• Can you see a time where you would be testing on multiple builds in a single session?

I can't think of a way that I can have the Scan tool "validate" the input in this section since the build identifier will be very different in different teams. So, the Scan tool will accept free-form text and assume the users don't enter invalid text here.

Still To Do:

• Where do we put this data? --> Need to know what the data looks like first. I am thinking about creating a new 'metrics' file in the 'reports' folder modelled after something simple like the 'testers.txt' file.

I am tentatively thinking the following:

• filename = builds.txt ("builds.csv" after I complete the CSV conversion issue)
• fields/row heading = "Session","Build ID"

This seems like a good start to me. What do you think?

[jfry]

Ahhh, good questions.

Expected format:

• I could imagine that allowing multiple build numbers might be useful for someone, someday. If it's easy I'd say sure...but I doubt it's that important.
• Likewise, maybe someone needs >1 line to capture a build, but I think it's pretty safe to expect the build to be a single line.
• I definitely agree that there's no real way for you to do validation. (I could see you allowing users to specify a regex that build ids need to match for their project...but this seems like a nice later addition, not needed for now.)

Output: Sounds fine to me.

[aquaman]

Story Done.

Files updated = 6:

• bin/scan2.rb, todomaker.rb, todomaker_win_xls.rb
• config/sbtm.yml
• doc/session_sheet_template
• submitted/create_new_session.rb

Metrics file outputs:

• charters.txt
• builds.txt (new)

NOTES:

• No input validation is currently performed. Free-form text is allowed.
• Multi-line input is allowed. Discouraged (charter should focus on a specific purpose, therefore single environment), but allowed.

[jfry]

Awesome, thanks!

On Thu, Jun 23, 2011 at 8:19 PM, aquaman < reply@reply.github.com>wrote:

Story Done.

Files updated = 6:

• bin/scan2.rb, todomaker.rb, todomaker_win_xls.rb
• config/sbtm.yml
• doc/session_sheet_template
• submitted/create_new_session.rb

Metrics file outputs:

• charters.txt
• builds.txt (new)

NOTES:

• No input validation is currently performed. Free-form text is allowed.
• Multi-line input is allowed. Discouraged (charter should focus on a specific purpose, therefore single environment), but allowed.

Reply to this email directly or view it on GitHub: https://github.com/aquaman/clr-sessions/issues/6#issuecomment-1430004

Jeff Fry

http://testingjeff.wordpress.com http://associationforsoftwaretesting.org