tag:blogger.com,1999:blog-19162830237524494612024-02-08T01:31:13.113+01:00Test experiencesAnonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-1916283023752449461.post-73212202600271572702012-05-09T14:41:00.001+02:002012-05-09T14:41:12.651+02:00Moved to wordpressI moved my blogging to <a href="http://jmengerink.wordpress.com/">http://jmengerink.wordpress.com </a>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com0tag:blogger.com,1999:blog-1916283023752449461.post-19182176874219803872012-03-09T17:15:00.002+01:002012-03-09T17:15:41.184+01:00Cloutest book launched<span lang="EN-US" style="mso-ansi-language: EN-US;">It has been quiet on my
blog, but it had a reason! Finally, after a year of work, the book Cloutest
about testing cloud services is done! Yesterday Polteq hosted a big event where
we launched our approach on how to test cloud services (IaaS, PaaS and Saas). In
the afternoon Kees Blokland and I gave a tutorial based on the book to our
Polteq colleagues. While we were introducing the approach, the external guests
were entertained by Lee Copeland. <o:p></o:p></span><br />
<br />
<span lang="EN-US" style="mso-ansi-language: EN-US;">In the evening, Lee started
with a keynote on innovations in the test world, after which Martin Pol
introduced the concept of the cloud. When he finished this introduction, it was
time for Ruud Teunissen to cover the architecture of Cloutest. Cloutest
consists of detailed risks that will occur when you start using cloud computing,
grouped into themes. Next to these risks you will find a set of test measures.
Some of them existing measures, like load testing, but nicely polished to fit
the new needs we see for performance testing in the cloud. But you’ll also see
new measures that stretch the definition of test. The important asset of the
book is the link we made from each individual risk to the different measures
needed to cover the risk. <o:p></o:p></span><br />
<br />
<span lang="EN-US" style="mso-ansi-language: EN-US;">Having the architecture
clear, Kees and myself started introducing some new risks we see with cloud
computing. And of course we also shared some measures with the audience e.g. on
how to test the elasticity that we find in the cloud and how to deal with rules
and regulations in different countries. <span style="mso-spacerun: yes;"> </span><o:p></o:p></span><br />
<br />
<span lang="EN-US" style="font-family: "Calibri","sans-serif"; font-size: 11pt; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">At the end of our event, all attendees received the
book Cloutest! Feels kind of strange that people now have a book with my name
on it on their <span style="mso-spacerun: yes;"> </span>bookshelves…</span><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgdosi4BzyOPrRiXVexxNZYwAx1_piMF6gMlZzakCl_r0NYU5ATrQg1ujOqX2p4XAPHnBDWuOPo2SF5SJZi15oZG9D_1tv-TOO1HZ90YoPUMN7zotLXRWsBxoZc4nzsHEt2bZEZ0Z1yStQo/s1600/Cloutest.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgdosi4BzyOPrRiXVexxNZYwAx1_piMF6gMlZzakCl_r0NYU5ATrQg1ujOqX2p4XAPHnBDWuOPo2SF5SJZi15oZG9D_1tv-TOO1HZ90YoPUMN7zotLXRWsBxoZc4nzsHEt2bZEZ0Z1yStQo/s320/Cloutest.png" width="245" /></a></div>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com0tag:blogger.com,1999:blog-1916283023752449461.post-87717488242437708792011-12-12T20:28:00.001+01:002011-12-12T20:31:03.343+01:00EuroSTAR 2011<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfqvMILSmoRMM3iFWNFndYP6by7p20xLbDjkaSi-BIYvCvuHuiLzG684Rb1a_8FjcAaU-sJY-TfVrrVBu8z4hXch663regSZvMMxRrtFYPM6VHAQb_ASMaVbcl4qO1MoyAS2_S6Oy3rq6d/s1600/EuroSTAR_2011.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="157" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfqvMILSmoRMM3iFWNFndYP6by7p20xLbDjkaSi-BIYvCvuHuiLzG684Rb1a_8FjcAaU-sJY-TfVrrVBu8z4hXch663regSZvMMxRrtFYPM6VHAQb_ASMaVbcl4qO1MoyAS2_S6Oy3rq6d/s400/EuroSTAR_2011.jpg" width="400" /></a></div>
While in China for <a href="http://www.polteq.com/">Polteq</a>, I wrote a submission for EuroSTAR 2011. The conference theme was "In the pursuit of quality" so I decided to go for a less explored subject "How To Test Mobile Applications". At the start of April I received an e-mail from the conference stating:<br />
<blockquote class="tr_bq">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;"><span style="font-family: "Courier New", Courier, monospace;">We are
delighted to inform you have secured a speaking slot at the 2011 EuroSTAR
Conference and we look forward to meeting you in Manchester later in the year.</span></span></blockquote>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;">So I got lucky enough to have my first submission to EuroSTAR accepted :-) The next months were needed to slowly build up the presentation (which also got accepted for Testnet). </span></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;">Tuesday the 22st of November we went to Manchester. The mist cancelled some flights, but our flight only had a delay of about 20 minutes. The first day we missed out on some presentations due to a slow restaurant, but I was able to hear Gojko Adzic speak about "Death To The Testing Phase". The main things I got from this presentation were that it is important to visualise quality and to apply post release testing. My colleague Kees Blokland was all day preparing for his presentation the next day.</span></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;">In the evening Dorien and I went to visit the local Christmas market. We were surprised to see a lot of Dutch stands there, supplying Dutch cheese, Dutch mini pancakes and more. The touristic route (read: we got a bit lost) back to the hotel took a while, but we saw some nice parts of Manchester.</span></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;">Wednesday I got to see more of the presentations. The day started with a keynote of James Whittaker: "Pursuing Quality? You Won't Get There By Testing". The story proved to be good, but only applicable to large companies. Smaller companies can't just use thousands of people to perform some beta testing like Google can...</span></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;">Next I went to one of the short tracks where Martin Mussmann told us about "Mind Maps As Part Of The Agile Testing Process". In the high change rate that he has to work in, mind maps proved to be a nice way to show the backlog items and connect test ideas to them. By describing only what to test and not how to do it, these maps could be used as a help in talking to both the business as the developers. </span></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;">I just had to attend Kees' presentation about "Chasing Quality In Cloud Computing - Testing Different Levels Of Quality Requirements". He showed us that using the cloud incorporates different types of risks that need to be mitigated. Of course the obvious ones like performance, security and functionality, but also new risks in the area of legislation and regulations and suppliers. After describing the risks he also described test measures to be taken. Ending with a description of the broader role of the test manager which needs involvement in selection, implementation and operation of cloud services.</span></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<span lang="EN-GB" style="mso-ansi-language: EN-GB;">Since automation is one of the topics I like, I also went to Julian Harty who introduces us to "Pushing The Boundaries Of User Experience Test Automation". He provided some nice examples of automatable user experience tests. Not everyone can (or will) use the mouse to navigate through websites, so tabbing and hotkeys should also be tested. We accept that the number of steps needed to perform a task by using the keyboard is more than with using the mouse, but there are limits. So also the number of tabs needed to return to the same point on a page should be limited, which can automatically be validated. </span></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
The closing keynote of wednesday was Daryl Elfield with "Power to the People - Achieve Fast, Sustainable Change in Quality by Harnessing the Crowd". He gave nice examples of how communities within the organisation not only provided ideas for change, but also created the footage to actually perform the change. So by giving power to the employees, the commitment to the company increased.</div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
In the evening our friends from Hauwei invited us to eat with them in Chinatown. It was really nice to have some decent Chinese food again :-) We went for hot pot! I chose the spicy one, but was uncertain of my choice when two out of three Chinese took the normal while saying that spicy was too spicy for them. The first couple of bites were extremely spice, but I got used to the taste and had a great dinner. </div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
Thursday started with Ben Walters' keynote "Create Customer Value with Agile Testing". I know I visited this keynote, but can't remember much of it. Probably I was too busy with preparing for my own presentation this day.</div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
I attended the presentation previous to mine by John Montgomery "What The Top 10 Most Disruptive Technology Trends Mean For QA And Testing". He described a nice list of disruptive trends like agile, cloud and mobile, but in my eyes lacked to really show what it meant for testing.</div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhMMhqKuzYETcSAMPLimRlnImFH5dQJXo2o0pXYki-pds_Ek57-9JCJZelc5XZHuSkCzs6iUMem9GqlLUtCTw5yv4nRwuZ7jghgsEuleYmpjSzLpSbhZ1JlPIK2J6TwIFsSRNZkkBmP-uyt/s1600/HearMeSpeakEuroSTAR2011.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhMMhqKuzYETcSAMPLimRlnImFH5dQJXo2o0pXYki-pds_Ek57-9JCJZelc5XZHuSkCzs6iUMem9GqlLUtCTw5yv4nRwuZ7jghgsEuleYmpjSzLpSbhZ1JlPIK2J6TwIFsSRNZkkBmP-uyt/s1600/HearMeSpeakEuroSTAR2011.png" /></a>Then finally my debut on the big stage with "How To Test Mobile Applications" ;-) A quick count showed more than 100 people in the audience, a new record since my 30 people audience at Testnet. I provided a road map for building mobile applications. Testing needs to be aware of store requirements, next to the normal business and user requirements. Another important part is that the impact of the app on the features provided by the phone and vice versa need to be tested. It would be a pity if the phone wasn't able to receive calls while using an app... After my presentation I had quite a lot chats with people that had attended and wanted to know more.</div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
<br /></div>
<div class="MsoNormal" style="margin: 0cm 0cm 0pt;">
My state of mind didn't allow me to take in any information after my presentation, so I took the rest of the afternoon strolling around the Expo. At the end of the afternoon we flew back home. I have really enjoyed my first visit to EuroSTAR and saw good presentations. I hope to attend again next year in Amsterdam.</div>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com0tag:blogger.com,1999:blog-1916283023752449461.post-72559700595569041812011-10-05T14:28:00.001+02:002011-10-09T10:09:58.311+02:00Testnet Fall Event<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgp69sE7Ysg0bRihvP6dCXLaRrUl7grWZVxpxlzTFv8iOqCvHNATQBlQPHGxZ-8NXnI7c_018VCyXd4LV-PvK5AB10UYAi7YBydWTdG3zk95k899y_uyhau56oYKUUSXIC7YulS3yhTpLEK/s1600/testnetlogo.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgp69sE7Ysg0bRihvP6dCXLaRrUl7grWZVxpxlzTFv8iOqCvHNATQBlQPHGxZ-8NXnI7c_018VCyXd4LV-PvK5AB10UYAi7YBydWTdG3zk95k899y_uyhau56oYKUUSXIC7YulS3yhTpLEK/s1600/testnetlogo.png" /></a><span style="color: black; font-family: Verdana, sans-serif;">
</span><span lang="EN-US" style="line-height: 115%; mso-ansi-language: EN-US;"><span style="color: black;"><span style="font-family: Verdana, sans-serif;">Yesterday I
attended the <a href="http://testnet.org/">Testnet</a> Fall Event. It proved to be an interesting as well as a
fun day! For the morning sessions I chose to attend an interactive session
about “The future of testing”. The session started with a couple of <a href="http://en.wikipedia.org/wiki/Pecha_Kucha">PechaKuchas</a> giving the presenters views on the future. After the last Pecha Kucha
the audience could pick the presenter with whom they wanted to discuss a bit more.
Since I liked the presentation about people the best, I ended up with <a href="http://www.huibschoots.nl/wordpress/">HuibSchoots</a>. We got into a discussion about training and skills needed by people.
The thing I best remember is: you need to take control of what you want to
learn and not wait until others suggest training. The next part of the morning
session dealt with personas, defined by the presenters, which could exist in
the future of testing. Again in little groups, the personas got more depth by
adding why people chose a certain persona. The last part of the, in my eyes
very successful, workshop existed of putting sticky notes with comments to other
personas than you chosen one. Providing extra questions and room to motivate
the personas better.<o:p></o:p></span></span></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="color: black;">
<br />
</span><span lang="EN-US" style="line-height: 115%; mso-ansi-language: EN-US;"><span style="color: black;">Next up was a
keynote by a non-tester, <a href="http://www.innoq.com/blog/st/about/">Stefan Tilkov</a>. He managed to give a clear description
of the cloud and in the end provided some pointers to testing. The rest of the
day existed of lots of presentations to choose from. I attended a couple and
have learned new views on the world of testing, providing me with a lot of food for thought. <o:p></o:p></span></span></span><br />
<span style="font-family: Verdana, sans-serif;"><span style="color: black;">
<br />
</span><span lang="EN-US" style="line-height: 115%; mso-ansi-language: EN-US;"><span style="color: black;">The last session of
presentations contained my own presentation about “How to test an APP”. I
expected only a few people, since my time slot was at the end of the day. That
turned out differently when about 30 people joined my session. The audience was
great! Interested and asking lots of questions.<o:p></o:p></span></span></span><br />
<span style="color: black; font-family: Verdana, sans-serif;">
<br />
</span><span lang="EN-US" style="line-height: 115%; mso-ansi-language: EN-US;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;"><span style="font-family: Verdana, sans-serif;">Between all
sessions there was enough time to talk to friends and meet new people. All the
ingredients for a great day! Thanks to Testnet for facilitating this great
event!</span> </span></span></span>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com0tag:blogger.com,1999:blog-1916283023752449461.post-53611928266595874472011-09-28T07:54:00.004+02:002011-10-05T14:47:56.095+02:00Cloud in testperspectief, testen in cloudperspectief<span style="mso-bidi-font-family: Verdana;"><span style="color: black; font-family: Verdana, sans-serif;">Usually I blog in English, but since this is my article as published in the Dutch magazine </span><a href="http://www.release.nl/"><span style="color: black; font-family: Verdana, sans-serif;">Release</span></a><span style="color: black; font-family: Verdana, sans-serif;"> (Jaargang 15, nummer 3), this post will be in dutch. </span></span><br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9nD52VO4EpR9K7cWjnwF_61KMEl6vu-vT-Xa_mw7SRZINwegH8sbxo_ijIyuh1I-t8Lzh1uqSr_gaaE6cRrouKXbmltd0KT9ro4y8Vdw-OEVV7Jk16rpg9Rexx821QvJhBb3nha767reL/s1600/cloud-computing2.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh9nD52VO4EpR9K7cWjnwF_61KMEl6vu-vT-Xa_mw7SRZINwegH8sbxo_ijIyuh1I-t8Lzh1uqSr_gaaE6cRrouKXbmltd0KT9ro4y8Vdw-OEVV7Jk16rpg9Rexx821QvJhBb3nha767reL/s1600/cloud-computing2.jpg" /></a><span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Cloud
computing, vaak kortweg de cloud genoemd, is niet meer weg te denken. De
aandacht die de cloud krijgt, heeft alle kenmerken van een hype, maar dat neemt
niet weg dat het een wezenlijke ontwikkeling is van de manier waarop ICT-diensten
worden verleend. Het afnemen van een cloud service is steeds vaker
aantrekkelijker dan eigen software maken of kopen. In de cloud wordt er alleen
betaald voor wat er wordt gebruikt (pay–per-use) en er kan flexibel capaciteit
worden bij- of afgeschakeld (elasticiteit). Kortom, steeds meer ICT verdwijnt
in de cloud en dat heeft invloed op testen en de rol van de testmanager. Cloud
computing introduceert nieuwe eisen en risico’s waarvoor een speciale
testaanpak nodig is. Hoe test je bijvoorbeeld elasticiteit?</span></span></span><br />
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;"><br />
Testen zelf verandert ook! Zo is er een significante rol weggelegd voor de
testmanager in het selectieproces. Dat is een belangrijke fase om tijdig vast
te stellen wat voor risico’s de gebruiker of de business loopt bij de keuze
voor een bepaalde cloud service. Die risico’s kunnen liggen op allerlei
vlakken. Dat is ook een verandering bij het testen: een accentverschuiving naar
niet-functionele aspecten. Het zoeken naar functionele fouten in de software
verschuift in de cloud naar de achtergrond.<o:p></o:p></span></span></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 0pt;">
<b><span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Nieuwe eisen en risico’s<o:p></o:p></span></span></span></b></div>
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Cloud
computing is volop in ontwikkeling. Het is dan ook een illusie om te verwachten
dat voor alle nieuwe eisen en risico’s al pasklare testoplossingen beschikbaar
zijn. Dit artikel beschrijft een aantal voorbeelden van cloud-specifieke
risico’s en bijbehorende testaspecten en is een beknopt fundament voor verdere
ontwikkeling.</span></span></span><br />
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;"><br />
<span style="mso-bidi-font-style: italic;">Cloud computing omvat nogal wat. Kijk
voor een goed bruikbare definitie op de website van het Amerikaanse NIST (</span></span></span></span><a href="http://www.nist.gov/itl/cloud/index.cfm"><span style="color: black; font-family: Verdana, sans-serif; mso-bidi-font-family: Verdana; mso-bidi-font-style: italic; text-decoration: none; text-underline: none;">www.nist.gov/itl/cloud/index.cfm</span></a><span style="font-family: Verdana, sans-serif;"><span style="color: black;"><span style="mso-bidi-font-family: Verdana; mso-bidi-font-style: italic;">).<br />
</span><span style="mso-bidi-font-family: Verdana;">Krachtige features van cloud
computing zijn elasticiteit en pay-per-use. Is er meer capaciteit nodig,
bijvoorbeeld omdat er meer gebruikers zijn, dan kan dat on-demand worden
geleverd. De gebruiker ziet dit vanzelf terug in de afrekening. Maar hoe kan er
getest worden of dit in de praktijk ook werkt? In de aanpak hiervoor is een
combinatie nodig van load testen (wisselend gebruik nabootsen en zien dat er
capaciteit bij komt en weer af gaat), grenswaardenanalyse (wat gebeurt er op de
grens van mijn ’bundel’) en procescyclustest (het handmatige aanvraagproces en
de financiële afrekening).<o:p></o:p></span></span></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 0pt;">
<b><span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Risico’s<o:p></o:p></span></span></span></b></div>
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Met de transitie naar de cloud
storten alle risico’s van het internet zich over de afnemer heen. Wat voorheen
geen issue leek (de server stond in het eigen gebouw), wordt in één keer een
punt van aandacht. Wie kan er allemaal bij mijn gegevens in de cloud? Hoe
veilig is het transport eigenlijk? Dit leidt niet tot nieuwe soorten
beveiligingstesten, maar security eist wel een nog belangrijkere plek op bij
het testen.<o:p></o:p></span></span></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 10pt;">
<span style="color: black; font-family: Verdana, sans-serif; mso-bidi-font-family: Verdana;">In
de public cloud kan de service trager worden als gevolg van de (piek)belasting
van andere afnemers. Als de leverancier een abonneemodel hanteert waarbij de
service wordt overboekt (dat levert meer winst op), dan is dat een goede reden
om een real-time loadtest uit te voeren. Daarmee wordt bedoeld: het uitvoeren
van de loadtest op het moment van de dag dat de piekbelasting zich naar
verwachting zal voordoen.</span></div>
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 0pt;">
<b><span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Nieuwe acceptatiecriteria<o:p></o:p></span></span></span></b></div>
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Cloud services worden mondiaal
aangeboden en daarmee komt een nieuw pakket van acceptatiecriteria om de hoek
kijken: voldoet de cloud service aan allerlei wet- en regelgeving? Zo is onder
meer het bewaren van privacygevoelige gegevens aan allerlei wetten en regels
gebonden. De testmanager zorgt ervoor dat er, in samenspraak met bijvoorbeeld
een jurist, een checklist van wettelijke controlepunten wordt samengesteld. Bij
het afvinken daarvan kunnen er complicaties aan het licht komen, zoals
conflicterende of onduidelijke wetgeving in bepaalde landen en de (on)betrouwbaarheid
van de overheid waar de cloud provider is gevestigd. Dit kan tot verrassingen
leiden, zoals in het voorbeeld van de Amerikaanse overheid die de Patriot Act
in stelling bracht om toegang te krijgen tot de gegevens van WikiLeaks.<o:p></o:p></span></span></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 0pt;">
<b><span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Beschikbaarheid<o:p></o:p></span></span></span></b></div>
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Wanneer een belangrijk business
proces afhangt van een cloud service, is de beschikbaarheid van de service van
groot belang. Als een cloud service leverancier (onaangekondigd) een wijziging
aanbrengt in de service, kan dat verstrekkende gevolgen hebben, zoals een
storing in de koppeling met andere systemen of handleidingen die plotseling
niet meer kloppen. In een end-to-end testopstelling kan de impact van
wijzigingen in een cloud service, maar ook in aangesloten systemen, worden
getest. Er is een groeiende noodzaak voor een continu draaiende, end-to-end
regressietest. Deze test moet niet alleen op functioneel gebied inzicht in de
risico’s bieden, maar ook op non-functionele aspecten, zoals performance. De
taak van de testmanager stopt dus niet na de implementatie, want ook in de
operatie moet er continu worden getest.<o:p></o:p></span></span></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 0pt;">
<b><span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Leveranciersaspecten<o:p></o:p></span></span></span></b></div>
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">De afnemer van cloud services
krijgt te maken met allerlei leveranciersaspecten. Wat gebeurt er bijvoorbeeld
precies met de gegevens in de cloud als de leverancier failliet gaat? Is er een
back-up scenario en, zo ja, is dat getest? Ook de migratie naar de cloud en van
de ene cloud service (leverancier) naar een andere moet worden getest. Als er
geen geteste migratiestrategie is, levert een afnemer zich over aan één
leverancier (vendor lock in).<o:p></o:p></span></span></span><br />
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 0pt;">
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Fenomenen die in de cloud hype
lijken mee te liften zijn Het Nieuwe Werken en Bring Your Own Device. Wordt de
ondersteuning van een veelheid van vaste en mobiele platforms een belangrijk
risico bij cloud computing of niet? De toekomst zal het leren.<o:p></o:p></span></span></span></div>
<br />
<div class="MsoNormal" style="line-height: normal; margin: 0cm 0cm 0pt;">
<b><span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Conclusie<o:p></o:p></span></span></span></b></div>
<span style="mso-bidi-font-family: Verdana;"><span style="font-family: Verdana, sans-serif;"><span style="color: black;">Voor de testmanager is een
belangrijke rol weggelegd bij de invoering van cloud computing. De testmanager
moet al in actie komen bij de selectie van cloud services. Maar ook na de
implementatie ervan loopt zijn rol door tot in de operatie van cloud
services. Centraal staan daarbij de risico’s en (test)gerelateerde maatregelen
om die risico’s te beheersen.<o:p></o:p></span></span></span>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com0tag:blogger.com,1999:blog-1916283023752449461.post-81378384558851482362011-08-30T16:47:00.001+02:002011-09-28T13:44:38.912+02:00Producing waste<span lang="EN-GB" style="mso-ansi-language: EN-GB;"><span style="font-family: Verdana, sans-serif;">Today a colleague pointed out that Agilistas produce a lot of waste. Since it's in the core of agile to reduce waste, this seemed like a strange statement. So we discussed a bit :-) I pointed out that we produce less overhead documentation than other people do, as can be found in almost all presentations about agile. <o:p></o:p></span></span><br />
<span style="font-family: Verdana, sans-serif;"><br /></span><br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGcrFku_rpdgW29k8vJ3v2lps-JrKQbqNzIWzlrQ-0Lgsjvn54oWgWDHeoEpuNTmmgX_VcjqyWS9Xn2Oro5iXhH8BXhpmvl8LK3khZSDFQfxx0rZQ3kbLMKKyINccssoT4IdSv6VNFTPQt/s1600/waste.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><span style="font-family: Verdana, sans-serif;"><img border="0" height="188" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGcrFku_rpdgW29k8vJ3v2lps-JrKQbqNzIWzlrQ-0Lgsjvn54oWgWDHeoEpuNTmmgX_VcjqyWS9Xn2Oro5iXhH8BXhpmvl8LK3khZSDFQfxx0rZQ3kbLMKKyINccssoT4IdSv6VNFTPQt/s200/waste.jpg" width="200" /></span></a><span lang="EN-GB" style="mso-ansi-language: EN-GB;"><span style="font-family: Verdana, sans-serif;">He then told me he didn’t mean in the projects themselves… Agilistas are responsible for a whole lot of blogposts, tweets, Google+-posts, etc. and he labelled it waste. Of course I responded that using <u>social</u> media is an act of being social. A trait of all true Agilistas, since we value communication. Using social media gives people the opportunity to read and reply in their own time and we win time by not using it for mindless discussions. This silenced him for a moment, but he’s still not convinced. Luckily I know the silence means I got him thinking. <o:p></o:p></span></span>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com2tag:blogger.com,1999:blog-1916283023752449461.post-75343560868730010622011-08-25T11:24:00.001+02:002011-09-28T13:44:51.640+02:00Soft skills<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmac2LcLHA68x25dHApcpRr_1OHVJRdXtuS89qXTknfyzBYLHWp6ma4Uhzt0mekyJAyWTBpDxOaGKUc7OxVyyy7fS6z32xKZEZ2Mt96uh3tudBp257CczXsMh3v4psR1Qwv7N92RDN8SD-/s1600/soft-skill.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="146" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhmac2LcLHA68x25dHApcpRr_1OHVJRdXtuS89qXTknfyzBYLHWp6ma4Uhzt0mekyJAyWTBpDxOaGKUc7OxVyyy7fS6z32xKZEZ2Mt96uh3tudBp257CczXsMh3v4psR1Qwv7N92RDN8SD-/s200/soft-skill.jpg" width="200" /></a><span style="font-family: Verdana, sans-serif;">Testing is a profession! As a profession it requires skills in testing techniques, domain knowledge for the specific case you are working on, etc. A often underappreciated skill is communication. From the test perspective you need to communicate with a lot of different types of people, where each type requires it's own approach. This seems simple, but is harder than it looks. It's not only the type you need to be aware of, but also the person itself. In some cases a direct approach is the way to go, where in other cases you need to dress up your comments. Be aware of what you say and to who you say it!</span> Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com0tag:blogger.com,1999:blog-1916283023752449461.post-2683110537117332622011-08-16T17:15:00.003+02:002011-09-28T13:45:08.434+02:00Agile and test planning<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgAMtmdyJNnjvBzCfUepqC4wtvBYaHp0p7lzIyMohm1P009ina8doWDQOGY3lmPafgFpXcuNuIoF8lR30JvUZicfSAKkE7bz0V9r-JGDqrx91CJo2rA07Vik20KQKhExvEjrlXtt3G9T_rX/s1600/planfirst.jpg" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="67" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgAMtmdyJNnjvBzCfUepqC4wtvBYaHp0p7lzIyMohm1P009ina8doWDQOGY3lmPafgFpXcuNuIoF8lR30JvUZicfSAKkE7bz0V9r-JGDqrx91CJo2rA07Vik20KQKhExvEjrlXtt3G9T_rX/s200/planfirst.jpg" width="200" /></a></div>
<span style="font-family: Verdana, sans-serif;">Agile is often used in combination with scrum, thus resulting in multidisciplinary teams and short release cycles. If we take these two points as a given, how do we adopt our test planning to be able to keep working? First I'll describe a way to work, then I'll give some pointers to take into account during the sprint planning.</span><br />
<span style="font-family: Verdana, sans-serif;"><br /></span><br />
<strong><span style="font-family: Verdana, sans-serif;">Specification</span></strong><br />
<span style="font-family: Verdana, sans-serif;">When detailing the product backlog items, make sure the whole team has the same understanding of it. After the first detailing, developers can start creating and product owner, tester and analyst/designer can go over the specifics of the detailing. Then designer and tester can start making their corresponding designs. When done creating the specifications designer and tester review each other's work to see if they described the same system. Any open questions after this reviewing should be resolved with the product owner.</span><br />
<span style="font-family: Verdana, sans-serif;"><br /></span><br />
<strong><span style="font-family: Verdana, sans-serif;">Execution</span></strong><br />
<span style="font-family: Verdana, sans-serif;">Start executing test scripts as soon as possible. Share testing knowledge with the developers, so that they benefit from this knowledge when creating the unit tests. Make sure you stay informed about what is delivered to the test environment and then prioritize your test cases according to what was in the last delivery. Usually when the pressure on test execution starts to build, the analysts/designers in your team will be less busy. They can help you execute the script you already designed. When developers have time left, ask them to automate the tests you want to run in continuous integration or regression.</span><br />
<span style="font-family: Verdana, sans-serif;"><br /></span><br />
<strong><span style="font-family: Verdana, sans-serif;">Bugs</span></strong><br />
<span style="font-family: Verdana, sans-serif;">Bugs can be solved quicker and with less documentation than in non-agile projects. Discuss bugs you find within your team. In this way all members learn about the bugs found and help each other to find solutions. If the bugs get fixed directly after you find them, it might not be necessary to document them. This results in less time tracking bugs.</span><br />
<span style="font-family: Verdana, sans-serif;"><br /></span><br />
<strong><span style="font-family: Verdana, sans-serif;">Sprint planning</span></strong><br />
<span style="font-family: Verdana, sans-serif;">With the sprint planning, keep in mind that you need time for specifying, executing, automating and retesting. To fit everything in the small amount of time, use specification techniques which result in a small number of test cases with high coverage. Make sure that developers also incorporate time for unit testing and for fixing bugs. In the case you will not do the automation yourself, make sure that the responsible person (sometimes the developers) will plan this time. </span><br />
<span style="font-family: Verdana, sans-serif;">Experience learns that setting some milestones for a sprint, e.g. first delivery start or code freeze, help the team to finish the sprint successfully.</span>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com0tag:blogger.com,1999:blog-1916283023752449461.post-41148612789327527612011-08-08T09:59:00.003+02:002011-09-28T13:45:52.202+02:00Locator problems<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhteIamL_mCK4PCypPTNFw8pB8te6_NIhQoTZMCsHTgVNptr5wUMv-O3UaOEAi8idPbbsUWKaYP_HZZNS90OLcVFfliSqXx0goeTkp6EMRLBZzoNY-6P_JjMcGF7g3bvCkGECLhwQOraiN3/s1600/Locator.jpg" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhteIamL_mCK4PCypPTNFw8pB8te6_NIhQoTZMCsHTgVNptr5wUMv-O3UaOEAi8idPbbsUWKaYP_HZZNS90OLcVFfliSqXx0goeTkp6EMRLBZzoNY-6P_JjMcGF7g3bvCkGECLhwQOraiN3/s200/Locator.jpg" width="199" /></a><span style="font-family: Verdana, sans-serif;">I'm still exploring using </span><a href="http://seleniumhq.org/"><span style="font-family: Verdana, sans-serif;">Selenium </span></a><span style="font-family: Verdana, sans-serif;">with page objects. For webelements that have an id or name tag it is easy to define the locators, but I'm having some problems creating a locator for some links. The xpath reference to the link, nicely supplied by </span><a href="https://addons.mozilla.org/en-US/firefox/addon/firepath/"><span style="font-family: Verdana, sans-serif;">FirePath</span></a><span style="font-family: Verdana, sans-serif;">, results in a "Unable to locate element". The link I'm trying to locate is in the format:</span><br />
<span class="nodeLabelBox repTarget " style="font-family: Verdana, sans-serif;"></span><br />
<blockquote>
<span style="font-family: "Courier New", Courier, monospace;"><<span class="nodeTag ">a</span><span class="nodeAttr "> <span class="nodeName ">href</span>="<span class="nodeValue ">xxx/yyy/</span>"</span><span class="nodeAttr "> <span class="nodeName ">title</span>="<span class="nodeValue ">yyy</span>"</span><span class="nodeBracket insertBefore ">>yyy</span></<span class="nodeTag ">a</span>></span></blockquote>
<span style="font-family: Verdana, sans-serif;"><br /></span><br />
<span class="nodeLabelBox repTarget "><span style="font-family: Verdana, sans-serif;">I'll just keep trying to find how to locate it. Next to that I'm going to start working on </span><a href="http://fitnesse.org/"><span style="font-family: Verdana, sans-serif;">FitNesse</span></a><span style="font-family: Verdana, sans-serif;">.</span></span>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com1tag:blogger.com,1999:blog-1916283023752449461.post-26071352577504890912011-08-01T11:13:00.003+02:002011-09-28T13:46:02.247+02:00Selenium<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJkk2Qa_V27aCY5N2vysUxtThXdJlQdLRB3Te1xK0uWXk5z_i34mr7mtXpMhcsFh5bwylJX4KuECqiT3alfFjCOq1Z4pCTbwVvzdUgQn8VX3EPk3GuE7rzOVc11OFLWJK2qS5iArB3PD3K/s1600/selenium.png" imageanchor="1" style="clear: right; float: right; margin-bottom: 1em; margin-left: 1em;"><img border="0" height="181" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhJkk2Qa_V27aCY5N2vysUxtThXdJlQdLRB3Te1xK0uWXk5z_i34mr7mtXpMhcsFh5bwylJX4KuECqiT3alfFjCOq1Z4pCTbwVvzdUgQn8VX3EPk3GuE7rzOVc11OFLWJK2qS5iArB3PD3K/s200/selenium.png" width="200" /></a></div>
<span style="font-family: Verdana, sans-serif;">Recently a collegue, Daniël Gollings, showed me Selenium. As an enthusiastic about test automation I was interested directly. So I started to follow the step-by-step tutorial he made. I downloaded all the needed compenents and started with Selenium IDE. Since I have a background in programming, I quicly switched to Selenium RC to be able to apply better control of the automation. The ease of setting up tests amazed me. </span><br />
<span style="font-family: Verdana, sans-serif;"><br /></span><br />
<span style="font-family: Verdana, sans-serif;">Recent conversations with Roy de Kleijn and Martijn de Vrieze, reignited the Selenium-fire. After following a webinar about page objects, I understand the concept. Now only experience can help me with applying the concept. Hopefully I can use my knowledge in a couple of assignments and broaden my knowledge.</span>Anonymoushttp://www.blogger.com/profile/00581193495052765585noreply@blogger.com2