TestingGuidance Forum Rss Feed

New Post: Updates

jzserai — Tue, 09 Apr 2013 20:07:29 GMT

I see there are still tags in the document meant to be updated at some point. Will there be updates? Will there be a volume 2 as suggested on the documentaion page?

Thank you

New Post: Completeness graphs tool

ptcmariano — Sat, 13 Oct 2012 11:54:29 GMT

I use TFS with agile template process http://msdn.microsoft.com/en-us/vstudio/aa718795.aspx

New Post: Some figures not showing in .pdf document.

iwcoetzer — Thu, 24 Dec 2009 10:23:47 GMT

Hi,

I'm using the latest version of Adobe Acrobat Reader > 9.2.0.

However some of the figures are not visible when I view the .pdf file using Adobe Reader.

For example:

Chapter 4:

Figure 1 & Figure 2 are not visible?

Is this a problem with the pdf document only? I can see the figures when browsing the guide on the code plex site.

New Post: Completeness graphs tool

bugmenot2 — Fri, 02 Oct 2009 07:24:41 GMT

How can i generate and mantain a Completeness Graph and deploy it on a intranet?

Thank you in advance

New Post: Feedback on BETA2 Release (June 30, 2009)

shanecourtrille — Thu, 03 Sep 2009 14:24:04 GMT

Page 30: What are "Wizard of Oz" tests?

New Post: Tooling

shivkumarsahu — Mon, 27 Jul 2009 12:10:38 GMT

Hey, I am waiting for the 2nd and 3rd releases of the series (Acceptance test automation guide and Tool support for acceptance test-driven development)...Are they already lounched or waiting for the completion?

Is there any old / previous version of the same available?

Thanks,

Shiv Kumar Sahu

New Post: Feedback on BETA2 Release (June 30, 2009)

asqui — Tue, 21 Jul 2009 07:16:22 GMT

Hello,

I noticed some minor typographical errors in the BETA2 release that came out on June 30:

Page 21: "Figure 2" label is split across lines. Probably needs a preceding linebreak.
Page 21: "One way to combat this is to break the project into increments of functional ."
Should that be 'functionality', or is there another word missing?
Page 23: "Figure 4" label is split across lines.
Page 23: "If the product owner finds bug, the developer fixes it as soon as possible"
Should that be 'If the product owner finds A bug'?
Page 23: "Figure 6 - Multi-Release Agile Project illustrates an agile project with two releases"
I think that should be referring to Figure 5, rather than Figure 6.

Pretty minor stuff, but I know it's these small things that become invisible once you've been working on something for a while so I thought it worthwhile to point them out.

I'm only up to Page 23 right now, so I'll report any further suggestions in this thread as I come across them.

Regards,
Daniel Fortunov

New Post: Feedback on Alpha Release

gmelnik — Sun, 02 Nov 2008 20:02:45 GMT

Gary, thanks for your feedback. This is still an early draft. We are trying to find a balance here between a dry reference book and a reader-friendly story telling. It's likely that the colloquialisms will be replaced in the final version of the guide.
Grigori

New Post: Feedback on Alpha Release

GaryVS — Thu, 04 Sep 2008 18:27:06 GMT

Thank you for the preview of the book; I am about halfway through, just finished the section on automated testing, and there are some great items in there and I very much enjoy your definitions and separation of models. One item that I immediately noticed was the use of idioms and colloquialisms, and I would suggest removing as many as possible. For example, an early reference to a binary decision being 'yea' or 'nay', or one line partially reading as "For the supplier to feel confident that their baby will pass muster with the customer requires...".

This is just my personal opinion but I feel that it decreases readability and of more importance lacks a certain professional tone/quality.

I am enjoying the book so far and I plan on monitoring future releases. I will try to provide more feedback once I have finished the book and had a chance to reflect on what I was able understand and fit into my own mental framework of acceptance testing and testing models.

Thanks,
Gary

Edited-removed formatting artifacts

New Post: Feedback on Alpha Release

MichaelPuleio — Wed, 27 Aug 2008 02:07:41 GMT

Thanks for your interest in the Acceptance Test Engineering guide.

This CTP is an incomplete draft of a book that is currently being written. We have included the entire Draft Table of Contents. However, there are a number of empty sections in the actual text. If you see an empty section, assume we will fill in the section before we complete the book.

Your feedback is invited. Simply reply to this thread. We will carefully read every piece of feedback.

Thanks,
The team of authors: Grigori, Jon, Gerard, Michael, Rohit

New Post: Feedback on Community Preview Aug 4, 2008

gmelnik — Mon, 04 Aug 2008 02:50:34 GMT

Thanks for your interest in the Acceptance Test Engineering guide.

This CTP is an incomplete draft of a book that is currently being written. We have included the entire Draft Table of Contents. However, there are a number of empty sections in the actual text. If you see an empty section, assume we will fill in the section before we complete the book.

Your feedback is invited. Simply reply to this thread. We will carefully read every piece of feedback.

Thanks,
The team of authors: Grigori, Jon, Gerard, Michael, Rohit

New Post: Feedback on Community Preview Jul 7, 2008

gmelnik — Wed, 16 Jul 2008 03:58:24 GMT

TOC Live show the flow of the content and is hyperlinked to all other sections packaged in the preview.
Regards,
Grigori

Optikal wrote:
I realize this is a work in progress, but it would still be nice if the document(s) could be organized into one structured pdf or docx file for reading when you make a public release...or even a numbered set of documents so we have some indication of a logical order to process the information in.

I'll try and give some more content-specific feedback once I finish going through all the content.

New Post: Feedback on Community Preview Jul 7, 2008

Optikal — Mon, 14 Jul 2008 19:42:14 GMT

I realize this is a work in progress, but it would still be nice if the document(s) could be organized into one structured pdf or docx file for reading when you make a public release...or even a numbered set of documents so we have some indication of a logical order to process the information in.

I'll try and give some more content-specific feedback once I finish going through all the content.

New Post: Tooling

MichaelPuleio — Fri, 11 Jul 2008 00:03:37 GMT

We are trying to stay fairly agnostic as far as the tooling we recommend in the first part of our guidance. Think of the guide we are currently writing as a foundation that we will build more guidance on, possibly including tooling recommendations and possibly new testing tools as well.

However, I would like to hear about your expereinces getting Fitnesse-type tests to work in TFS/VSTS. I had played with a similar idea a few years ago with an add-in for VS2005 and had some success.

Enjoy,
Michael Puleio -- patterns & practices
http://blogs.msdn.com/mpuleio

New Post: Feedback on Community Preview Jul 7, 2008

MichaelPuleio — Thu, 10 Jul 2008 23:58:33 GMT

We would love to hear your feedback on the Preview we posted. Just respond to this thread, and we will read your opinion and take your input under consideration.
Thanks,
Michael Puleio -- patterns & practices
http://blogs.msdn.com/mpuleio

New Post: Tooling

HakanForss — Fri, 20 Jun 2008 21:19:01 GMT

We are currently using FITNesse for some of our acceptance testing. It is a manual step for our testers to run them. I would really like to be able to run them as part of our CI Build in TFS and have the results to be part of the build report.
One solution for this problem that I have been thinking of is moving the FITNesse pages into TFS as a new testing type that would use HTML pages or something similar for authoring. Then you could manage them, run them and report on them as all the other tests.
What do you think? Would this be useful for you?

NEW POST: Definition of Acceptance Testing

karlmet — Tue, 20 May 2008 20:27:08 GMT

I like your definition very much. I see it as a simple and concise version of this one from Ward Cunningham :

"A formal test conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system."

NEW POST: Definition of Acceptance Testing

rodclaar — Mon, 12 May 2008 23:41:15 GMT

Most features, requirements and concepts in a proposed software project should be viewed top-down for most of the project. From that perspective your definition is correct, but it does not go far enough. When we breakdown or unfold the features, the "acceptance of a system" is too general. Acceptance Testing can be thought of as the definition of a test from the customer perspective, but it could be at any level visible to the customer or user. As long as the goal of the test specification is definable in user terms, we have an Acceptance Test.

NEW POST: Definition of Acceptance Testing

MichaelPuleio — Fri, 18 Apr 2008 20:50:34 GMT

We have a working definition. This definition is framing how we are approaching this space. Please let us know what you think of it:

Acceptance Testing: Planned evaluation by a customer (or customer proxy) to determine whether a system satisfies their expectations.

Thanks,
Michael Puleio - patterns & practices
Blog – http://blogs.msdn.com/mpuleio/
Web – http://msdn.microsoft.com/practices/