Flush out Mark's document as test suite

[ibuchanan]

[JogoShugh]

The intention of a Functional Test Suite is to test the product from the perspective of the End User, to ensure that it behaves as expected.

Mark's doc is here: https://github.com/versionone/VersionOne.Client.VisualStudio/blob/master/SupportTests/Tests.md/

Unit Testing versus Functional Testing

Unit Tests are written from a programmers perspective. They are made to ensure that a particular method (or a unit) of a class performs a set of specific tasks.

Functional Tests are written from the user's perspective. They ensure that the system is functioning as users are expecting it to.

Source: http://www.softwaretestingtricks.com/2007/01/unit-testing-versus-functional-tests.html

Automated Functional Testing

Functional tests can be automated given the right tools and libraries to drive the UI.

Joe had started investigating the newer MS tools, documented here: http://msdn.microsoft.com/en-us/library/dd286726.aspx

More general info

• http://www.infoq.com/articles/gui-automation-patterns
• http://help.utest.com/testers/crash-courses/functional/test-case-writing-creation-101

[ibuchanan]

We have since documented more about the happy path but we did not turn it into a test suite. It doesn't seem practical to do so at this time so I'm closing as "wontfix".