2018 up to now | 2017 | 2016 | 2015 | 2014 | 2013 | 2012

Mailing List - Entries from 2018 up to now

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        mso-believe-normal-left:yes;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><![if mso 9]><style>p.MsoNormal
        {margin-left:3.0pt;}
</style><![endif]><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="margin-left:3.0pt;margin-top:3.0pt;margin-right:3.0pt;margin-bottom:.75pt">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Could you give an example of the type of set-up procedure you’ve created?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Again thanks Rutger…and thanks to all responders.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Bob Schmidt<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Dijk, van, Rutger [mailto:RL.Dijk@portofrotterdam.com]
<br>
<b>Sent:</b> Tuesday, February 01, 2011 5:02 AM<br>
<b>To:</b> Weston Gross; Bob Schmidt; Martin Moser<br>
<b>Cc:</b> qftest-list@qfs.de<br>
<b>Subject:</b> RE: [QF-Test] QF Test - Managing Automation - Best Practices<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Hello,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">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.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">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.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">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.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">At the moment, our end-users don't create tests themselves. We created a few workflow-tests to guide them in their test activities.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">With regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Rutger van Dijk<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Port of Rotterdam<o:p></o:p></span></p>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="margin:0in;margin-bottom:.0001pt;text-align:center">
<span lang="NL" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in">
<b><span lang="NL" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Van:</span></b><span lang="NL" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> qftest-list-bounces@qfs.de [mailto:qftest-list-bounces@qfs.de]
<b>Namens </b>Weston Gross<br>
<b>Verzonden:</b> woensdag 26 januari 2011 2:23<br>
<b>Aan:</b> Bob Schmidt; Martin Moser<br>
<b>CC:</b> qftest-list@qfs.de<br>
<b>Onderwerp:</b> Re: [QF-Test] QF Test - Managing Automation - Best Practices<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">"How does the QA Automation practice fit or integrate itself within an Agile development organization?"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">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.
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><br>
>>> Martin Moser <martin.moser@qfs.de> 1/25/2011 12:43 AM >>><br>
Hi Bob,<br>
<br>
during my customer visits I recognized that it's really important, that you <br>
establish at least one engineer in your team who is capable of <br>
understanding the technical issues like component recognition and scripting <br>
in detail.<br>
Then most customers tend to organize their test-suites in smaller modules, <br>
similar to recommendation from the Best-Practices chapter. This approach <br>
allows the people to keep the "technical" issues in the technical layer and <br>
the business testers implement their tests in separate test-suites re-using <br>
some parts from the basic layer.<br>
So, what I tried to say, is that you need something like a "QF-Test <br>
Professional/Lead/Power user" in your team for supporting the normal user. <br>
I personally think that's really a must-have in staffing.<br>
<br>
I'd also recommend that your team can talk to the actual developers of your <br>
SUT, if it's required. Talking about test-cases and some approaches for <br>
testing sophisticated or complex GUI-parts might make everyone's life <br>
easier.<br>
<br>
I hope anyone else could share his/her experience in setting up QF-Test.<br>
<br>
Best Regards,<br>
Martin<br>
<br>
--On Mittwoch, Januar 12, 2011 12:00:45 -0500 Bob Schmidt <br>
<bob.schmidt@invisioninc.com> wrote:<br>
<br>
> Hello:<br>
><br>
> I'm interested in drawing on and learning from any experiences or<br>
> recommended best practices and processes that one can use to create an<br>
> organization that will enable continued growth and maintenance of<br>
> automation within the company.<br>
><br>
> How does the QA Automation practice fit or integrate itself within an<br>
> Agile development organization? What staffing considerations must be made<br>
> to sustain the infrastructure built thus far? What are "must-haves" in a<br>
> 6 month/12 month automation rollout roadmap?<br>
><br>
> Thank you in advance for your feedback.<br>
><br>
> Sincerely;<br>
><br>
> Robert Schmidt<br>
><br>
> This communication and attachment(s) are the confidential property of<br>
> INVISION, Inc.  If you are not the intended recipient, please notify the<br>
> sender immediately and delete this message; any copying, dissemination or<br>
> use of these contents by persons other than the intended addressee(s) is<br>
> prohibited.  Thank you.<br>
><br>
> _______________________________________________<br>
> qftest-list mailing list<br>
> qftest-list@qfs.de<br>
> <a href="http://www.qfs.de/mailman/listinfo/qftest-list">http://www.qfs.de/mailman/listinfo/qftest-list</a><br>
<br>
<br>
<br>
-- <br>
Martin Moser                           martin.moser@qfs.de<br>
Quality First Software GmbH            <a href="http://www.qfs.de">http://www.qfs.de</a><br>
Tulpenstr. 41                          Tel: +49 8171 38648-14<br>
DE-82538 Geretsried                    Fax: +49 8171 38648-16<br>
GF: Gregor Schmid, Karlheinz Kellerer  HRB Mnchen 14083<br>
<br>
_______________________________________________<br>
qftest-list mailing list<br>
qftest-list@qfs.de<br>
<a href="http://www.qfs.de/mailman/listinfo/qftest-list">http://www.qfs.de/mailman/listinfo/qftest-list</a><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="margin:0in;margin-bottom:.0001pt;text-align:center">
<span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray">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@portofrotterdam.com).<br>
Havenbedrijf Rotterdam N.V., Rotterdam, is geregistreerd bij het handelsregister in Nederland onder nummer 24354561.<br>
<br>
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@portofrotterdam.com).<br>
Havenbedrijf Rotterdam N.V., Rotterdam, is registered with the trade register in the Netherlands under no. 24354561.<br>
<br>
www.portofrotterdam.com</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""><o:p></o:p></span></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1">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.<br>
</font>
</body>
</html>