Three Amigos Session on Test Cases for Visual Studio Client

[JogoShugh]

The old version of the Visual Studio Client is documented here:

http://versionone.github.io/VersionOne.Client.VisualStudio/

We want to:

• Install the old version (probably for VS 2010)
• Understand how it works
• Create outline of Test Cases / Living Documentation for the new, updated 2012 Version

[JogoShugh]

Acceptance Criteria:

• Carlena, Ian, Mark Irvin feel confident that the Test Cases documentation are helpful and complete for intended use of the client
• The old client can be installed, and used by all developers on the openAgile team against a sample V1 project.

[JogoShugh]

Note: I'll start this

[JogoShugh]

Notes on this in wiki at: https://github.com/versionone/VersionOne.Client.VisualStudio/wiki/Functionality-notes-and-test-cases

[ibuchanan]

After this first three amigos session we have a first draft for specifying the Workitem Owners. It still lacks a scenario for how the UI should list the owners. My thoughts from the first session:

• Considering the agile testing quadrants, I perceive our biggest area of risk to be "supporting the team" and "technology facing". It's not that we have the other quadrants covered, but when we find problems from other quadrants that require code changes, we can't even make those changes quickly and confidently (where confidence is just about basic things like avoiding exceptions). I think we share this concern which lead us to trying to write specs that weren't much more than unit tests.
• I feel the specs "smell bad". They seem to be tightly coupled to specifying the UI as opposed to explaining what a user is trying to accomplish. If we're going to spec a UI by example, mock-ups seem far more effective than Gherkin. And if we want to automate testing whether the implementation meets the spec, then we need those mockups to be some kind of DSL. Could we do this with Balsamiq?
• There is a need for some specs regarding the owners list but I think we should do that at the service level, where the spec defines a service interface that we expect from the VersionOne application.

[ibuchanan]

Trying to spec the whole client is just too big of a task so I'm marking this issue invalid. We should do 3 amigos for every issue as a matter of habit. And, that might also mean, writing examples for features that already exist. We will just take that on an issue by issue basis.