2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007

(older archive entries before 2007 are not shown here, but included in the onsite-search)

Mailing List - Entries of 2011


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [QF-Test] QF Test - Managing Automation - Best Practices


  • Subject: Re: [QF-Test] QF Test - Managing Automation - Best Practices
  • From: Bob Schmidt <bob.schmidt@?.com>
  • Date: Tue, 1 Feb 2011 16:31:22 -0500

Thanks Rutger…getting developers to sign up for overall testing responsibilities has been a challenge here. We’re new to Agile so it’s all part of the growing pains.

Could you give an example of the type of set-up procedure you’ve created?

Again thanks Rutger…and thanks to all responders.

Regards;

Bob Schmidt

 

 

 

From: Dijk, van, Rutger [mailto:RL.Dijk@xxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, February 01, 2011 5:02 AM
To: Weston Gross; Bob Schmidt; Martin Moser
Cc: qftest-list@?.de
Subject: RE: [QF-Test] QF Test - Managing Automation - Best Practices

 

Hello,

 

At our company we have three developmen-teams buidling our new information system. We hired a test-specialist who has a lot of knowledge about QF-Test and he shares his knowledge with the team members. This way, all teams have sufficient knowledge for setting up test suites and automating tests. And with team members I mean both developers, business analysts, designers and architects.

 

Creating a shared responsibility for the product quality is essential, otherwise only the test-specialist will run the tests. Both developers and testers need to understand and work together in creating the product. This means that the correct naming of components and scripting is part of a shared goal: creating high quality software.

 

We've created some setup-procedures in a set so that they can be called from the other test-suites. Some tests are also added to the continuous integration (Hudson) which makes them run every night.

 

At the moment, our end-users don't create tests themselves. We created a few workflow-tests to guide them in their test activities.

 

With regards,

 

Rutger van Dijk

Port of Rotterdam

 


Van: qftest-list-bounces@?.de [mailto:qftest-list-bounces@?.de] Namens Weston Gross
Verzonden: woensdag 26 januari 2011 2:23
Aan: Bob Schmidt; Martin Moser
CC: qftest-list@?.de
Onderwerp: Re: [QF-Test] QF Test - Managing Automation - Best Practices

"How does the QA Automation practice fit or integrate itself within an Agile development organization?"

 

In my situation, testers wanted prerequisite data to be entered into the application to get them to a point where they could continue manually testing. I set up generic procedures that could handle the entry depending on the data that went into the test script. I was able to run scripts on hundreds of IDs which saved the testers many hours of setup.


>>> Martin Moser <martin.moser@?.de> 1/25/2011 12:43 AM >>>
Hi Bob,

during my customer visits I recognized that it's really important, that you
establish at least one engineer in your team who is capable of
understanding the technical issues like component recognition and scripting
in detail.
Then most customers tend to organize their test-suites in smaller modules,
similar to recommendation from the Best-Practices chapter. This approach
allows the people to keep the "technical" issues in the technical layer and
the business testers implement their tests in separate test-suites re-using
some parts from the basic layer.
So, what I tried to say, is that you need something like a "QF-Test
Professional/Lead/Power user" in your team for supporting the normal user.
I personally think that's really a must-have in staffing.

I'd also recommend that your team can talk to the actual developers of your
SUT, if it's required. Talking about test-cases and some approaches for
testing sophisticated or complex GUI-parts might make everyone's life
easier.

I hope anyone else could share his/her experience in setting up QF-Test.

Best Regards,
Martin

--On Mittwoch, Januar 12, 2011 12:00:45 -0500 Bob Schmidt
<bob.schmidt@?.com> wrote:

> Hello:
>
> I'm interested in drawing on and learning from any experiences or
> recommended best practices and processes that one can use to create an
> organization that will enable continued growth and maintenance of
> automation within the company.
>
> How does the QA Automation practice fit or integrate itself within an
> Agile development organization? What staffing considerations must be made
> to sustain the infrastructure built thus far? What are "must-haves" in a
> 6 month/12 month automation rollout roadmap?
>
> Thank you in advance for your feedback.
>
> Sincerely;
>
> Robert Schmidt
>
> This communication and attachment(s) are the confidential property of
> INVISION, Inc.  If you are not the intended recipient, please notify the
> sender immediately and delete this message; any copying, dissemination or
> use of these contents by persons other than the intended addressee(s) is
> prohibited.  Thank you.
>
> _______________________________________________
> qftest-list mailing list
> qftest-list@?.de
> http://www.qfs.de/mailman/listinfo/qftest-list



--
Martin Moser                           martin.moser@?.de
Quality First Software GmbH            http://www.qfs.de
Tulpenstr. 41                          Tel: +49 8171 38648-14
DE-82538 Geretsried                    Fax: +49 8171 38648-16
GF: Gregor Schmid, Karlheinz Kellerer  HRB München 14083

_______________________________________________
qftest-list mailing list
qftest-list@?.de
http://www.qfs.de/mailman/listinfo/qftest-list

 


Voor elektronische communicatie hanteert Havenbedrijf Rotterdam N.V.(HbR) een disclaimer. U kunt deze nalezen op de internetsite van het HbR of opvragen via info@?.com).
Havenbedrijf Rotterdam N.V., Rotterdam, is geregistreerd bij het handelsregister in Nederland onder nummer 24354561.

Havenbedrijf Rotterdam N.V.(HbR) has a disclaimer with regard to electronic communication. You can read the disclaimer on the internet site of the HbR or ask for a copy by mail to info@?.com).
Havenbedrijf Rotterdam N.V., Rotterdam, is registered with the trade register in the Netherlands under no. 24354561.

www.portofrotterdam.com



This communication and attachment(s) are the confidential property of INVISION, Inc. If you are not the intended recipient, please notify the sender immediately and delete this message; any copying, dissemination or use of these contents by persons other than the intended addressee(s) is prohibited. Thank you.