Our team is looking for a test management tool. Bluntly we are not ready for automation yet. Essentially we want a tool for scripting and test monitoring/management. Something like Rational Manual Tester or Mercury TestDirector.
Our developers will be moving to Visual Studio, and it has been suggested that we should too.
While Visual Studio does seem to have some good automated, load testing and unit testing functionality - it seems from my uninformed perspective to be a bit sparse on the manual testing front. Or am I missing something?
Has anyone any experience in using VSS for manual testing?
(I've searched this forum with the term "manual" and only got one result).
A manual test in VS2005 is a text file that you enter the test steps, expected results, etc. When you execute one or more manual tests within VS, you will be given a dialog for each test. In the dialog, you read and execute the test, choose Pass or Fail, and enter any extra info. VS will create .trx files with the Pass/Fail results - similar to those created for automated unit tests. If you post the results to Team Server, then you can generate the same reports available to the developers.
We've not used the manual tests here, so I can't say how effective this approach is.
I have used that manual test function in TestPartner and I would imagine that manual test functions are similar in all tools. Its really just another place to document the manual test. The advantage is that everything is kept together.
The disadvantage for me is that I find MS word a lot easier to use but that may not be applicable to everyone.
I did some checking, and VS2005 has an option to create the manual tests in either text or Word format. If created in Word format, it is creating .mht files (MHTML documents.) By default, the document is associated with IE, but you can open them in Word without issue.