Test planning using Camano

Test planning using Camano - Click & Solve

Test planning using Camano - Click & Solve — Tue, 17 Feb 2009 12:37:05 GMT

PingBack from http://www.clickandsolve.com/?p=9358

re: Test planning using Camano

Clemens Reijnen — Tue, 17 Feb 2009 15:24:50 GMT

is this the new layout of camano? are their any large changes...

re: Test planning using Camano

Amit Chatterjee — Tue, 17 Feb 2009 16:40:26 GMT

Responding to Clemens - yes, this the current and new layout of camano. We have made some big simplications of the model. As the tool is still under development, we may do some more changes to the user experience.

re: Test planning using Camano

Erik Steiner — Thu, 19 Feb 2009 16:49:37 GMT

I really like the integrated concepts I saw so far. Just one thing should be taken care of: Getting test reports easily out of TFS to be printed and signed off.

Using VSTS2008 I am currently struggling with two problems:

- Putting (unit-) test results into a word document.

- Managing manual test cases and reporting the results.

For the first I use a xslt file for transforming the trx file of a test run and then copy the resulting html table into a word document. Not nice, but working.

For the latter, I use a test case work item instead of manual tests, because I can much better put this information into an excel spreadsheet, which provides for a good tool for documentation for other stakeholders who cannot access TFS. And, that spreadsheet can be put into a document management system, be printed and approved by signature. This is especially neccessary for regulated projects, e.g. medical device development, and companies relying on paper based documentation (which are many of the really big ones I know.)

Quite useless for my *report* are the links between specifications and related test cases, because this info is not available in Excel. Additionally, I would like to report at least the IDs of the linked bug work items of failed test cases.

For the time being we put some effort into manually transferring the IDs of the links into text fields, so that we have that information available in the spreadsheet.

Eventually, I would like to have a spreadsheet containing the following columns: test case ID, referenced spec ID(s), test case title, test case description, tester, test result, referenced bug ID(s), ...

As said initially, I like the upcoming stuff and can't wait to have them available. I even like the current possibilities when being online. The only really frustrating thing is to get meaningful reports out of TFS easily. There is always a lot of manual work just for the reporting.

Regards,

Erik Steiner

re: Test planning using Camano

Amit Chatterjee — Fri, 20 Feb 2009 20:53:47 GMT

Erik - I am glad you like the integrated concepts.

Reporting will be much better in VS2010. I will add a post on reports to this series and highlight the capabilities there.

re: Test planning using Camano

Jean Brandenburg — Mon, 02 Mar 2009 23:51:32 GMT

For Test Planning, I would like to see Requirement (ex: actual associated requirement/s for this test case, PreCondition (ex: user must have admin or manager rights) and Expected Results (ex: user should be able to add/update/delete a record, etc.) added. I would like to be able to export it to a Word doc. I assume you can enter a defect that will be associated to this test case and the code files used to correct the problem discovered.

re: Test planning using Camano

Abhishek Thakur — Thu, 07 May 2009 16:42:10 GMT

One aspect that I could not clearly identify was whether the test plan and test execution cycle are one-and-the same.

In my prior roles, we dealt with test suites and then we had test execution plans which picked test cases from the test suites.

This separation provided some benefits:

A. Both the test suites and test execution plan allowed the setup / environment to be modified. This included passing environmental variables to be used by automated test cases. E.g. for quad code machine the timing interval could be set to a factor of 5 i.o. default 2. Or extra setup steps could be done if the plan was executed on XP vs. Vista.

B. The test case related metrics could help the planner decide whether to include the test in daily run or weekly run etc. E.g. number of bugs caught by a test case across test runs helped move the test case from P3 to P1 or P0.

Elevating the Role of the Tester with Visual Studio 2010

Ed Glas's blog on VSTS load testing — Tue, 19 May 2009 19:55:04 GMT

I am very excited proud and proud to introduce the new testing features you’ll find in dev10. In addition

Microsoft Dynamics AX Software Design Review and Knowledge Transfer

Dave Froslie - Microsoft Development on the Prairie — Tue, 26 May 2009 23:53:11 GMT

I spent a week in early May at the Software Design Review (SDR) / Knowledge Transfer at our Microsoft

re: Test planning using Camano

Juan Trujillo — Thu, 03 Sep 2009 03:01:03 GMT

Hi Amit,

My question is regarding access to the Test Plan by other stakeholders of the project that might or might not have access to VSTS 2010. Is there a way to make them public ? Is there a way to publish them in Sharepoint ?

Thank you and congratulations for the product.