<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lyon Testing on Medium]]></title>
        <description><![CDATA[Stories by Lyon Testing on Medium]]></description>
        <link>https://medium.com/@TestingLyon?source=rss-1ac9792d7922------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*tYtGX7-G8SSQlOEoPluuww.png</url>
            <title>Stories by Lyon Testing on Medium</title>
            <link>https://medium.com/@TestingLyon?source=rss-1ac9792d7922------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:30:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@TestingLyon/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A (former) tester interview — Stephen Janaway]]></title>
            <link>https://medium.com/lyon-testing/a-former-tester-interview-stephen-janaway-29da5e02e817?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/29da5e02e817</guid>
            <category><![CDATA[testers]]></category>
            <category><![CDATA[tester-role]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[manager]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Fri, 12 Apr 2019 11:51:43 GMT</pubDate>
            <atom:updated>2019-04-12T11:51:43.179Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*8fcBlL6-RzrxMRJ0-hy2zw.jpeg" /></figure><h3>A (former) tester interview — Stephen Janaway</h3><p>For this new interview, we have the pleasure of introducing<br> you a very specific profile, Stephen Janaway.</p><p>Stephen evolved from various testing-focused roles, such as<br> test manager or test coach, to different positions whose testing is only a part of the iceberg, such as delivery manager.</p><p>‘Leaving’ testing if you move towards a different role ?</p><p>Not really.</p><p>At least, not exactly. Stephen shares his vision with us.</p><p><strong>Who are you, what are you doing, where are you working?</strong></p><p>I’m Stephen, I’m VP Engineering at Bloom &amp; Wild, a startup based in London. We’re changing the way people send flowers and hopefully spreading some joy in the world as a result.</p><p><strong>Your current role is ‘VP Engineering’ : could you describe in a few lines what it is about?</strong></p><p>It’s Engineer whispering mostly 🙂 Well to be more serious, I lead a team of really talented developers and testers who help to make Bloom &amp; Wild the success that it is. I do a lot of recruitment, team building and management, and sometimes even get my hands dirty in code or testing. Basically everything that helps us deliver to our commitments and “keep the trains running on time”.</p><p><strong>How would you define your ‘relationship’ between your current position and testing?</strong></p><p>Once a tester, always a tester 🙂 When I’m involved then it’s more in acceptance of stories now rather than leading testing efforts earlier in the lifecycle, and it’s more the exception that I get involved, but when I do I really still enjoy it. As a manager of testers, as well as developers, then I get to pass on some of my experience as well.</p><p>If I had to put a score to how involved I am now, it’s a 3. I’m as involved with development, running teams and hiring and people management as anything else. But as a small company then almost everyone gets involved when required.</p><p><strong>You also previously worked in testing-related roles ; Could you quickly describe those different roles?</strong></p><p>My career is fairly typical I’d say, I started off as a developer, realised I liked testing more then moved into Test Lead, Test Manager and Senior Test Manager roles at various different companies. I ended up heading up a large Quality group in Nokia for some years which was more about managing the Test Managers and more about the conference calls and meetings than the testing. So I chose my next testing role in a different industry, luxury fashion, and went back to managing testers across various different teams. My final role in testing was as a Test Coach, working across a 250 person Technology team.</p><p><strong>Amongst those testing roles, which one did you prefer? Could you also give us a few reasons why?</strong></p><p>Good question. All of them had their good and bad points; if I had to pick one then the last Test Manager role was the most different. The tools and techniques were similar but the industry was so very different and exciting, and the company was much smaller than I’d previously been used to (although far larger than Bloom &amp; Wild) and so every day was more of an adventure.</p><p><strong>What was your first role which was not solely focused on the testing activity?</strong></p><p>After a brief period as a Test Coach I moved into a Delivery Manager role; this meant managing a whole development team, and acting as their scrum master as well. There was lots of cross-over from my previous roles so the move felt like a natural one to take.</p><p><strong>Why did you take that curve and how did you feel about ‘leaving’ a testing-focused role?</strong></p><p>I could see the end for Test Management as a role — as teams moved over to be cross functional and use Agile methodologies then the role of a Test Manager seemed obsolete. Functional management, whether development or testing, just doesn’t fit with cross functional teams and that results in either frustration, or makes it really hard to support the testers, who are spread across teams and therefore don’t have the day-to-day touchpoints with their manager.</p><p>Also, if you do the same thing, which in my case was the management of testers, for years then it felt like a good time to push myself and try something new. It also helped that the project that the team was working on was very exciting and new.</p><p><strong>Would you recommend to try this different point of view in a career?</strong></p><p>I’ve found it fulfilling and haven’t regretted it so in that sense I would recommend it. I think that it’s also very important that those of us who have a good grounding in testing get ourselves out into teams to influence and show people what good, context-driven, testing is. Far too many people working in technology just don’t know what good testing looks like.</p><p>I think it’s also worth pushing your boundaries and trying something new, rarely does life turn out worse as a result.</p><p><strong>Within your current position, could you give us a precise example of reactions you have which are conditioned by your testing background?</strong></p><p>I’m always aware of the Michael Bolton quote “Is there a problem here?” and I find that in my head in so many different circumstances. Whether it’s working with the team to plan and prioritise a backlog or testing/ accepting a story then I always find that my testing background helps me. I think testers also have a greater understanding of the products that they work on than most others involved, and so my testing background has really helped me to understand why, and how, I can keep a whole product view.</p><p>A lot of my role involves working with people and some of the skills I’ve needed as a tester, such as building and maintaining relationships and being able to explain what some people could perceive as negative, have really helped. There’s not an awful lot that’s different between explaining a bug to someone who really doesn’t want to listen, and getting them on board, to needing to explain deadline changes or team issues to stakeholders.</p><p><strong>What challenges do you think the test teams at Bloom&amp;Wild face within the software product team? Do you help overcoming them?</strong></p><p>We don’t have a test team as such, our two testers work across our three development teams. So that means there’s a bit of task switching sometimes and we have to be really careful that we’re not overloading them. We try as much as possible to make testing and quality a team activity and that means we aren’t reliant on our testers for everything that’s released but can instead make risk based decisions on what needs testing and why.</p><p><strong>What drives you crazy in the common misconceptions about testing?</strong></p><p>That testing is just pushing buttons and takes place once code is written. Getting involved as early as possible and helping teams own quality is what good testers do. I also get slightly irritated by the term ‘manual tester’, after all I don’t see automated development so I guess most of my team are ‘manual developers’.</p><p><strong>Tell us an anecdote while you had a testing-focused role (good or bad time, incredibly hard bug to reproduce or analyse …)</strong></p><p>I used to test the phonebook application on Nokia feature phones (the sort that used to sell in millions in the 2000’s, were indestructible and had Snake). One of our test automation suites was using one of my friends phone books as test data and we were calling his Mum up twice a day by mistake! This carried on for months. The lesson I learnt here — never use any old data you have as test data.</p><p><strong>If you were to recruit a tester in the team, what would you look for in a candidate for this role?</strong></p><p>I look for curiosity and an ability to learn. If a tester can explain to me what good testing is, and they talk about how they design and run software experiments or ask questions of the software then I’m really happy. Just don’t mention writing lots of test cases upfront and then running them once you’ve got the software to test.</p><p><strong>If you were to start again in a test-focused role, what advice would you give to juniors?</strong></p><p>Find the external test community and conferences as soon as you can. You’ll find friends, mentors and realise how much good testing there is out there. It took me 10 years to find the test community and it really opened my eyes to how my approaches weren’t good enough and how I could improve. I also made some great friends and had a lot of fun too.</p><p><strong>Do you have models, people inspiring you (testers or not)?</strong></p><p>I’m heavily inspired by Jerry Weinberg and it was so sad when he died in 2018. His work, both on testing, software and systems thinking, and people in general have really resonated with me over my career. My testing approach owes a lot to the context driven school of testing and the work of James Bach, Michael Bolton and Cem Kaner.</p><p><strong>What revolution should the testers be prepared for?</strong></p><p>I see more and more teams and companies that think that they don’t need testers but the testing industry seems really badly prepared in it’s response. In a way it does not surprise me, testers can get much better at explaining the value that they bring. I think that we are going to end up in place in the future where there are less testers, but good testers shouldn’t be worried. If you take an adaptive approach, get involved as early as possible in the software lifecycle, and remember that testing is much more than just testing the software then you’ll demonstrate your value.</p><p>Good testers help teams own quality and that’s something that we should all remember.</p><p><em>Originally published at </em><a href="https://lyontesting.fr/en/a-former-tester-interview-stephen-janaway/"><em>lyontesting.fr</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29da5e02e817" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/a-former-tester-interview-stephen-janaway-29da5e02e817">A (former) tester interview — Stephen Janaway</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview of a tester #4 — Maria Kedemo]]></title>
            <link>https://medium.com/lyon-testing/interview-of-a-tester-4-maria-kedemo-3efd52d9cbc0?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/3efd52d9cbc0</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Fri, 16 Feb 2018 12:50:39 GMT</pubDate>
            <atom:updated>2018-02-16T12:50:39.204Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YPLqQNNoZU6Wb_aFI_IpOw.jpeg" /></figure><p>After Julien, Thierry and Stéphanie, <a href="https://twitter.com/mariakedemo">Maria Kedemo</a> from Sweden is the fourth tester to kindly answer our questions.</p><h3>Who are you, what are you doing, where are you working?</h3><p><em>I have just started my own company as a freelancer. It was quite a tough decision. There are a few risks associated to it and also some new skills to be acquired to run a company. However I find it very exciting and I am embracing my new challenge.</em></p><p><em>Being a freelance offers me a freedom where I can be my own boss and decide over my future. I will focus mainly on software testing but with my experiences from different practices in software development I can also offer a broader service where training and coaching is something I am very passionate about. I am looking to get a balance between consultancy assignments and training sessions.</em></p><p><em>I currently have an interesting assignment at IKEA in Sweden where I am part of a very important e-commerce program. Though I have a formal title I focus on using my experience and skills to help IKEA transform their ways of working to become agile and deliver their solution a lot quicker than done today. My focus is on how testing fits in this transformation but since testing is only one part of software development I make sure to question the entire process and not only test related problems.</em></p><p><em>I am also active in the testing community. My current focus is on providing value as an elected board member of</em><a href="https://www.associationforsoftwaretesting.org/"><em> Association Software Testing (AST) </em></a><em>which is a non-profit organisation who views software testing as a cognitively complex activity that requires critical thinking, effective communication, and rapid self-directed learning. I am also the program chair for CAST 2018 which is a conference that have been organised every year since 2006 by AST.</em></p><p><em>Since I will be very busy this year with AST and my new company I currently only have one conference (Romanian Testing Days) where I will be doing a Keynote called Testing through time and space.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3i0Z8c0Cz4ft28aoQrYqXg.jpeg" /><figcaption>Testing Cup</figcaption></figure><h3>Looking back, and if you were to start again as a tester, what advice would you give?</h3><p><em>I wish I would have found the testing community a lot earlier than I did. I have had so much support and guidance from the context driven testing community and now other testing and development communities as well. Don’t be afraid to ask for help or to approach new people. Most people are very helpful. Though each problem is different I have found it very useful to discuss particular testing related issues or software development problems with my peers from all over the world to gain new insights.</em></p><h3>How would you describe your work to a 6-year-old?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZhNoZwAjUK668-zclxOZVw.jpeg" /><figcaption>Kid Speak</figcaption></figure><p><em>I describe my work as someone who helps people in IT to make valuable software, products that people wants to use and that they like. I describe how I get people together and talk to each other. Software development is actually more about the people than the technology. But I also try to explain my job as someone who teaches and help people to learn and become better to spot problems in software. The easiest way to describe to a 6-year old is actually to sit together and explore a product and talk about potential bugs. We would talk about, why is it bug or why isn’t it a bug. I believe that true testing skills must be demonstrated through practice.</em></p><h3>If you were to recruit a tester, what would you look for in a candidate for this role?</h3><p><em>When recruiting a tester I have looked into communication skills, both written and spoken. We often forget that software is created to solve people’s problems or help people with something. It’s a complex process because people have different needs. Communicating why you are testing something and why something in the product might be a problem (a bug) requires great communication skills. Social skills are required to understand people and what their needs are.</em></p><p><em>I have also been looking for how testers approach a problem. When I have recruited testers, the interview always consists of a conversation and practical exercises focused around testing. I do expect testers to both understand logical reasoning and lateral thinking. Many people seem to think that testing either requires to think “out of the box” or vertical thinking, but you need both.</em></p><p><em>I have also been looking for an eagerness to learn and to reflect and improve their skills. This is however harder to identify in an interview. The exercises might show some of that ability. I rarely focus on what tools the person have experienced or what technology the person is familiar with because the mindset is more important. If you are quick to learn and understand you can always learn new tools or languages etc.</em></p><p><em>The context of recruiting does matter though. If I’d recruit for a short-term contract it might be more important to know the specific tool or technology used in that assignment.</em></p><h3>Tell us an anecdote of your life as a tester (good or bad time, incredibly hard bug to reproduce or analyse…)</h3><p><em>There is one particular episode which I am very proud of. Many years ago I worked as a test manager in a project where we were supposed to integrate a 3rd party system with my client’s product. The approach used was a typical waterfall and requirements written in Word were sent back and forth in between the client and the supplier who sat in a different time zone. Time was ticking but it was very important to get an approval ton the requirements. Once that was in place development could start. I can’t remember exactly the frequency of the deliveries but when they happened we never got what we wanted. Bug reports were sent back and forth and when the bugs were fixed they were not what my client expected, or new bugs were introduced. In addition bugs were fixed here and there based on what the supplier thought was important. The process was very slow and as all projects we had a deadline to reach.</em></p><p><em>I suggested something very bold at that time. It might have seemed obvious for many but it was new to my client. I suggested that I together with one of our developers went to work on site with the supplier. After some heavy convincing we went to the supplier’s office to work together. By running exploratory testing sessions together with the supplier we could help them understand what was important to us as client. By participating in the bug-fix sessions we could help them prioritise and cluster their bug-fixes. By doing this we managed to reach the deadline we were aiming for. This was a great experience. Funny enough Agile was never mentioned in this way of working. To be honest I don’t even think I was aware of the methodology then but how to get the project working was common sense to me.</em></p><h3>What drives you crazy in the common misconceptions about testing?</h3><p><em>It’s strange how many misconceptions about testing still exists. One which drives me crazy is a more general one about testing where it is seen as assuring quality. Testing can’t assure quality. It gives you information about how the system you are testing might or might not work.</em></p><p><em>The second thing that drives me equally crazy are the misconceptions around exploratory testing where many people think it is ad-hoc and unstructured. These two misconceptions are something I have to explain daily.</em></p><h3>Do you have models, people inspiring you (testers or not)?</h3><p><em>I have many people inspiring me in different areas and levels. I actually don’t want to list anyone because I might miss someone. In fact most people have something which inspires. It might be their braveness or persistency or their ability to communicate to mention a few different things.</em></p><h3>How do you keep learning?</h3><p><em>I read blogs and articles, I watch different talks and I am part of many different social media where I get both inspiration and the ability to chat with peers.</em></p><h3>Cite one or more tools that have become essential to you?</h3><p><em>A few tools I often use are greenshot, liceCap, Xmind, post-its and my words (my language).</em></p><p>Thanks Maria. Do not hesitate to comment if you want to continue the debate on one of the subjects. We will soon have another guest interview.</p><p><em>Originally published at </em><a href="https://www.lyontesting.fr/en/interview-of-a-tester-4-maria-kedemo/"><em>www.lyontesting.fr</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3efd52d9cbc0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/interview-of-a-tester-4-maria-kedemo-3efd52d9cbc0">Interview of a tester #4 — Maria Kedemo</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feedback from Nordic Testing Days conference — Speaker perspective]]></title>
            <link>https://medium.com/@TestingLyon/feedback-from-nordic-testing-days-conference-speaker-perspective-22cdf8c6fd0a?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/22cdf8c6fd0a</guid>
            <category><![CDATA[public-speaking]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Tue, 18 Oct 2016 12:39:19 GMT</pubDate>
            <atom:updated>2016-10-18T12:39:19.152Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“Software testing conferences are so expensive that the best way to attend one is to be selected as a speaker.”: those have been my words for the last years. Having been selected as a speaker, I headed to Tallinn, the capital of Estonia, in June 2016, for a promising 2-days conference that I had been recommended by one of my previous managers as being one of the best he ever attended in Europe.”</em></p><p>If you have read my first article about this conference as an audience member, you may have already been convinced that this conference is awesome to attend! You may however still need to be persuaded that it is also a really good experience to be a speaker there; In that case here are few points detailing my feedback as a presenter.</p><h3>Gita on Twitter</h3><p>Share you knowledge, even if only to small groups @francoislenotre #NTD2016</p><p><strong>Why going so far away for a testing conference?</strong></p><p>Of course you don’t have to go that far to have an opportunity at presenting a topic in software testing! However, since there are many testing conferences in western Europe, you may wonder why I decided to apply at a conference so far away from France… my following points will explain my decision.</p><p><strong>Submission — No need to ‘categorize’ your topic</strong></p><p>I wanted to present the software testing teaching experience I had with an NGO while traveling to Cambodia in June 2015 <em>(article available </em><a href="http://www.francoislenotre.com/"><em>on my blog</em></a><em>). </em>Therefore, my topic was a bit unusual in the sense that it did not happen at work, and was very orientated towards personal development and pedagogic skills rather than just testing softwares.</p><p>Most of the call for papers sections of the conferences contained a tiny drop-down with few values inside: they were asking to categorize my talk. I literally struggled to fit my proposal under the categories offered: ‘Automation’, not at all… Category ‘Agile’ then? Why not, but my teaching unfortunately did not have time to cover Agile processes… The only one that could have roughly fitted would have been “Methods” or “processes”. I honestly don’t remember exactly which conferences offered that option, but they were very few.</p><p>Nordic Testing Days was the only conference I could find at that time that did not have this ‘category column’ constraint. It was one of the only call for papers still opened in November, and I remember reading instructions similar to …. “Well, we are just looking for some very unusual and awesome topics!”. Sold!</p><p><strong>Additional cost was an important factor</strong></p><p>At the time of my application, I was still looking for a new job in a brand new area I had just settled in, which means that I needed to pay for any additional cost not covered by the conference.</p><p>This was a very important factor.</p><p>Most of the conferences provide a standard ‘pack’ when you are a speaker: you usually get access to the whole conference except the tutorial days; You then have to pay for any dinner, social night out with the other testers.</p><p>NordicTestingDays was one of the very rare conferences to also provide the accommodation, as well as dinner and evening drinks, along with a DJ set. I was very pleased! It would allow me to reduce the budget.</p><p><strong>As a speaker, I really felt valued</strong></p><p>I really felt valued at the NordicTestingDays conference through a collection of small details which really made a difference: a warm welcome, a special speaker badge and the attention from the organizers when I had questions or worries before going on stage made me feel they cared a lot.</p><p>A final detail was the cherry on top of the cake: they offered a tiny gift to each speaker at the end of their talk, in front of the audience; And what a gift! Some fine marzipan coming from the best marzipan maker in Tallinn: Kalev!</p><p><strong>The right place to rehearse before the talk</strong></p><p>A big advantage of having the accommodation in the same place as where the event is held, is that you can go and rehearse your talk, have a rest and relax before your show time. I took a bit of time off early afternoon to do that, and I felt in good conditions when my turn came. Try to aim for the same event configuration if you are subject to stress before going on stage.</p><p><strong>Up on stage…</strong></p><p>My talk was at 5pm. The room was huge for the little audience I had, but I estimated to around thirty people attending. Going on stage is a special experience as you see the room from a completely new perspective, and, the most scary feeling, as you can see below, the spotlights are on you!</p><h3>Gita on Twitter</h3><p>@francoislenotre experience talk about teaching software testing #NTD2016</p><p><strong>Few advices during the presentation</strong></p><p>Speak slower than you think you do, as your heartbeat increases due to the stress, speeding up your voice automatically. It is a weird thing to do, but trust me it works. I tried it following the advice of Stephen Janaway, who is a regular speaker and also my previous manager, and it helped me breathing and getting my messages through.</p><p>If you are afraid of being distracted by looking at the audience into the eyes, aim at looking just above everyone’s head, at the ‘line of horizon’ (that is how I call it). This technic will make the audience feel like you give them attention, but also will avoid you distraction.</p><p><strong>After the talk</strong></p><p>Besides being relieved that my talk was done, and much more interesting than having to answer questions that may throw you off balance sometimes, I got interesting feedback from some participants regarding their own experience with teaching. They thought the topic was really interesting and were happy to see that, despite of the many rules that can exist in European countries making teaching nowadays really difficult, it was still possible to use innovative and efficient methods to raise smart people.</p><p>For more information about the topic I presented, you may view<a href="https://atlas.mindmup.com/2016/06/ad482a100afe013408e1093ddda541fa/sharing_testing_culture_in_cambodia/index.html"> a mindmap of it</a> realised by Dan Billing, a.k.a @thetestdoctor (see his <a href="https://twitter.com/TheTestDoctor/status/738381509254615041">original Tweet</a>)</p><p>Plus, after a few weeks, you get the feedback from the organizers who have gathered your audience thoughts, which is really nice and helps you to progress towards your next talk!</p><p><strong>To put it in a nutshell…</strong></p><p>I would really advise this conference for people who are not used to speak in public. The organization really values your participation and really helps you to get sorted with everything you need, so that your talk experience can occur in the best conditions. If you are still a bit shy after my encouraging article, you can still try the lightning talks, which will be a first step as being a speaker. After all, we all have to start somewhere!</p><p><em>Originally published at </em><a href="https://www.lyontesting.fr/en/feedback-from-nordic-testing-days-conference-speaker-perspective/"><em>www.lyontesting.fr</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22cdf8c6fd0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mesurer facilement le temps de chargement d’une page web — console web]]></title>
            <link>https://medium.com/lyon-testing/mesurer-facilement-le-temps-de-chargement-dune-page-web-console-web-fee15db9641e?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/fee15db9641e</guid>
            <category><![CDATA[test-de-performance]]></category>
            <category><![CDATA[test-web]]></category>
            <category><![CDATA[outil]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Tue, 13 Sep 2016 21:19:27 GMT</pubDate>
            <atom:updated>2016-09-23T12:19:15.014Z</atom:updated>
            <content:encoded><![CDATA[<p>Un temps de chargement trop long ou un écran qui rame et l’utilisateur va automatiquement quitter le site aussi vite qu’il est venu (on estime à 4 secondes le <a href="https://kinsta.com/learn/page-speed/">temps d’attente maximum</a> pour un utilisateur web). Mais avant même que l’utilisateur arrive sur votre page il faut qu’il la trouve et les robots comme <em>Google bots</em> auront tendance à mieux référencer les sites se chargeant en moins de 2 secondes.<br>Il est donc très important de prendre en compte le temps de chargement d’une page web.</p><p>Il existe différentes façon de mesurer le temps de chargement d’un page web.<br>On retrouve:</p><ul><li>la console navigateur</li><li>des outils en lignes</li><li>des plugins</li><li>un outil de tir de performance</li></ul><p>Le site exemple va tout simplement être le site framasoft qui effectue la promotion de logiciel libre <a href="https://framasoft.org/">Framasoft</a></p><p>Dans cet article il va être question de la première méthode “la console navigateur”, les autres exemples seront détaillés dans d’autres articles.</p><p>Cet outil très puissant (mais aussi usine à gaz) permet d’avoir une mesure très précise du temps de chargement d’une page Web en détaillant chacun des appels de la page. (Incluant Javascript).<br>Pour cela on va se plonger dans les navigateurs Chrome/Firefox/Edge et leur console.<br>De plus je suis sur un réseau fibré donc mon temps de chargement sera plus rapide que sur un téléphone en EDGE par exemple.</p><ul><li>Chrome</li></ul><p>Pour accéder à la console il suffit d’ouvrir Chrome puis de cliquer sur F12. La console ci-jointe devrait s’ouvrir</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/0*_z3pkUYxUljCIVy2.png" /></figure><p>Ensuite il faut cliquer sur Network, cocher le cache “disable cache” puis lancer la recherche de la page cible; l’ensemble des données de l’image se charge.<br>Vous devriez avoir une image comme celle-ci.<br>L’information recherchée se situe en bas de l’écran soit “Load : 1.96 s” en rouge, cette donnée correspond au temps de chargement de la page.</p><figure><img alt="Capture du 2016-08-30 11-22-53" src="https://cdn-images-1.medium.com/max/1024/0*o9AZH1JrwXtQYVXk.png" /></figure><p>Simple non ?</p><ul><li>Firefox</li></ul><p>C’est le même principe que pour Chrome, on accède à la console développeur via le bouton F12</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/0*CATC-yaJeIK8fMKc.png" /></figure><p>Ensuite il faut cliquer sur Réseau et là on remarque qu’il n’est pas possible de vider le cache comme sur Chrome. Quand on effectue la mesure du temps de chargement d’une page web, il faut à tout prix vider son cache pour ne pas avoir de donnée restantes, ce qui pourrait fausser les temps de chargement (notamment si votre page contient des images). Une des solutions est de passer en navigateur privée.<br>Après être passé en navigation privée on rouvre la console puis on va sur l’onglet Réseau, ensuite on effectue la recherche de la page cible, l’ensemble des données de l’image se charge.</p><p>Vous devriez avoir un résultat proche de celui-ci:</p><figure><img alt="Capture du 2016-08-30 11-51-06" src="https://cdn-images-1.medium.com/max/1024/0*10yNzMej2b-PvMXd.png" /></figure><p>L’information recherchée se situe en haut de l’écran il est noté “1.40s”, cette donnée correspond au temps de chargement de la page. On constate que le navigateur Firefox a chargé plus rapidement la page web (25% plus vite).</p><p>Pour montrer l’importance du cache voici la même page rechargée (donc avec des données dans le cache)</p><figure><img alt="Capture du 2016-08-30 11-55-53" src="https://cdn-images-1.medium.com/max/1024/0*85PcyEn-1bR1RAFg.png" /></figure><p>0.9s avec le cache contre 1.4s sans le cache le gain ici est de plus 35% mais va aussi beaucoup fausser vos résultats.</p><ul><li>Edge</li></ul><p>On reste sur le même schéma. On clique sur F12 et l’écran ci-joint devrait apparaître</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*2Wb7UNcCd-2RNG-_.png" /></figure><p>Ensuite il suffit de cliquer sur Réseau puis de ne pas oublier de vider le cache en cliquant sur le bouton ci joint</p><figure><img alt="Capture" src="https://cdn-images-1.medium.com/max/43/0*8LHNp2mkIDc3Cd5I.png" /></figure><p>puis d’effectuer la recherche de la page cible, l’ensemble des données de l’image se charge.<br>Vous devriez avoir une image comme celle-ci.</p><figure><img alt="Capture" src="https://cdn-images-1.medium.com/max/1024/0*yv6rTi29jnonJg0N.png" /></figure><p>L’information recherchée se situe en bas de l’écran il est noté “Load : 1.63 s”, cette donnée correspond au temps de chargement de la page.</p><ul><li>Conclusion</li></ul><p>L’utilisation de la console pour mesurer le temps de chargement des pages webs est une des méthodes les plus précises. Elle permet de bien distinguer les différents éléments qui compose une page web notamment les données JS qui sont de plus en plus présentes dans les sites d’aujourd’hui avec une démocratisation du material design.</p><ul><li>Pour aller plus loin</li></ul><p><a href="https://developers.google.com/web/tools/chrome-devtools/profile/network-performance/resource-loading#view-network-timing-details-for-a-specific-resource">Comment mesurer le temps de chargement depuis la console Google</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fee15db9641e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/mesurer-facilement-le-temps-de-chargement-dune-page-web-console-web-fee15db9641e">Mesurer facilement le temps de chargement d’une page web — console web</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Easily measure the load time of a web page — Web console]]></title>
            <link>https://medium.com/lyon-testing/easily-measure-the-load-time-of-a-web-page-web-console-24facae75332?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/24facae75332</guid>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[web-testing]]></category>
            <category><![CDATA[load-testing]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Tue, 13 Sep 2016 21:16:37 GMT</pubDate>
            <atom:updated>2016-09-23T12:19:04.100Z</atom:updated>
            <content:encoded><![CDATA[<p>A long load time to display your web page may unfortunately frustrate the user who will leave the website (the <a href="https://kinsta.com/learn/page-speed/">maximum waiting time</a> tolerated is estimated to 4 seconds approximately). Even before landing on your page, the user has to find your website and <em>Google Bots</em> will tend to reference it better if the loading time is below 2 seconds.</p><p>It means the loading time of a web page is a critical feature.</p><p>There are various ways to measure the load time of a web page. For example:</p><ul><li>the console in the browser</li><li>on-line websites</li><li>browser plugins</li><li>specific tools measuring loading time</li></ul><p>We will use framasoft website as an example. <a href="https://framasoft.org/">Framasoft</a> promotes Free software in France.</p><p>This first article will introduce “the console in the browser”, other ways will be detailed later on.</p><p>This very powerful (but also very complex) tool allows a very precise measure of the loading time by detailing each request/response within the page (Including Javascript ones).<br>We will see developer consoles in browsers Chrome, Firefox and Edge.<br>Moreover, I am using an optical fiber network so results will be faster than with a Smartphone with EDGE network for example.</p><ul><li>Chrome</li></ul><p>To access the console open Chrome and click on F12. The following console should appear at the bottom</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/0*Vs8ZA8L9AVeSV_kP.png" /></figure><p>Then, click on Network, select the check-box “disable cache” and process the search of the page tested, all data will be displayed.<br>You should see a result as the one in the screenshot below.<br>The total loading time is available at the bottom of the screen, “Load: 1.96” in red in this case.</p><figure><img alt="Capture du 2016-08-30 11-22-53" src="https://cdn-images-1.medium.com/max/1024/0*KMPZp7IeiF6xIXQ1.png" /></figure><p>Easy no?</p><ul><li>Firefox</li></ul><p>Just like with Chrome, we access the console [by pressing ‘F12’]</p><p>Then, click on Network notice that it is not possible to “disable cache” just like we did before with Chrome. When we measure the loading time of a web page, it is important to empty the cache in order to not have any previous data remaining. This would distort the loading time (especially if your page contains images). One solution is to use private browser.<br>After going in private navigation mode, reopen the console, then click on the Network tab and execute the search of the tested page; all the image data is now loading.<br>You should have a similar view to this picture:</p><figure><img alt="Capture du 2016-08-30 11-51-06" src="https://cdn-images-1.medium.com/max/1024/0*CepovM8cy_WnVZDV.png" /></figure><p>The total load time of the page is at the top of the screen, which is “1.40s “ in this case. We can see that the Firefox browser has loaded the web page 25% faster.</p><p>To show the importance of the cache, here is the reloaded page (which includes data in the cache)</p><figure><img alt="Capture du 2016-08-30 11-55-53" src="https://cdn-images-1.medium.com/max/1024/0*sBf4YjfsVo_G6Uui.png" /></figure><p>0.9s with the cache compared to 1.4s without the cache, this is 35% faster but results are distorted.</p><ul><li>Edge</li></ul><p>Same thing than other browsers. We click on F12 and this screen will be displayed</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*bcLpoQmU7g0HZdSE.png" /></figure><p>Simply click on Network do not forget to clear the cache by clicking on the button</p><figure><img alt="Capture" src="https://cdn-images-1.medium.com/max/43/0*bHH_mMUvSbjtq1IB.png" /></figure><p>, then load the page, and all data should load in the same way as shown below</p><figure><img alt="Capture" src="https://cdn-images-1.medium.com/max/1024/0*DRSDRhGBMdMmunfM.png" /></figure><p>The total load time is at the bottom of the screen, which is “Load : 1.63 s” in this case.</p><ul><li>Conclusion</li></ul><p>The use of the console for measuring loading time of web pages is one of the most accurate methods. It allows to distinguish the different elements which compose a Web page, including JS data that is more and more part of today’s websites with the democratization of material design.</p><ul><li>More information</li></ul><p><a href="https://developers.google.com/web/tools/chrome-devtools/profile/network-performance/resource-loading#view-network-timing-details-for-a-specific-resource">How to measure load time from Google console</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24facae75332" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/easily-measure-the-load-time-of-a-web-page-web-console-24facae75332">Easily measure the load time of a web page — Web console</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conférence Nordic Testing Days 2016 — Ma vision en tant que participant]]></title>
            <link>https://medium.com/lyon-testing/conf%C3%A9rence-nordic-testing-days-2016-ma-vision-en-tant-que-participant-bf815fe8ae4a?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf815fe8ae4a</guid>
            <category><![CDATA[non-classé]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Tue, 30 Aug 2016 08:38:47 GMT</pubDate>
            <atom:updated>2016-09-23T12:19:09.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Nordic Testing Days 2016" src="https://cdn-images-1.medium.com/max/198/0*6lTrm8eI0rnVGEml.png" /></figure><p><em>Les conférences sur le test logiciel se sont propagées très rapidement ces dernières années. Presque tous les pays en Europe ayant la leur, il peut devenir difficile de faire son choix pour assister à ce genre d’événements.</em></p><p><em>Après avoir eu un très bon retour de la conférence Nordic Testing Days en Estonie de la part d’un de mes anciens managers, j’ai décidé de suivre sa recommandation: eh bien, je n’ai pas du tout été déçu. Voici un petit résumé du contenu de ces deux jours de conférence auxquels j’ai participé.</em></p><p>Il est 9h du matin, ce jeudi 2 Juin, à Tallinn, la capitale de l’Estonie: le public est rassemblé dans la plus grande salle et attend le démarrage de l’événement avec impatience. La présidente de l’organisation monte sur scène, démarre son discours, et dans les cinq minutes qui suivent elle annonce: “On a énormément de nourriture pour les testeurs qui sont venus ici, parce qu’on ne veut pas de testeurs affamés: ils pourraient commencer à ‘démolir’ les logiciels!”.</p><p>L’annonce produit son effet, l’audience rit. La journée promet d’être intéressante.</p><p><strong>Une audience différente</strong></p><p>Nordic Testing Days représente l’intérêt de brasser un public très différent de celui des conférences d’Europe de l’Ouest: la plupart des professionnels viennent des pays baltes — Lituanie, Lettonie et Estonie — ainsi que des pays scandinaves. Il s’agit d’une excellente opportunité de rencontrer de nouveaux visages et d’élargir son réseau professionnel, ainsi que d’approcher le test logiciel de par la perspective de ces nouveaux utilisateurs; certaines des sessions sont justement focalisées sur leur expérience propre.</p><p>Comme bien souvent, cette conférence réunit également ce que j’appelle l’équipe usuelle du Royaume-Uni, qui regroupe des testeurs habitués à présenter des sujets dans diverses conférences en Europe. Je peux citer par exemple Bill Matthews, Dan Billing ou encore Stephen Janaway.</p><p><strong>Qu’est-ce qui est ressorti des sessions?</strong></p><p>Avoir le monopole ne doit pas empêcher la qualité</p><p>L’Estonie est surnommée «e-Estonie», surnom qui traduit l’émergence du pays comme l’une des e-sociétés les plus avancées au monde. La session de keynote introduisant la conférence, présentée par Andres Kütt, a souligné cet aspect: Andres est architecte numérique et travaille pour le gouvernement Estonien; Il collabore dans la fourniture de services électroniques pour les secteurs vitaux qui viennent s’interconnecter, tels que la santé ou des institutions de droit. Ceci implique qu’il faut considérer les besoins et les contraintes de ces secteurs afin de fournir des solutions utiles.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeqTvXuMLClw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeqTvXuMLClw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeqTvXuMLClw%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1866e8dd7ab35a0fbfb43af470724687/href">https://medium.com/media/1866e8dd7ab35a0fbfb43af470724687/href</a></iframe><p>Andres a insisté sur le fait de considérer, lorsqu’on recherche à améliorer la qualité de ses services, l’ensemble de l’écosystème qui les utilise: les utilisateurs, les secteurs, les exigences et contraintes différentes qui en émanent. Etant le seul fournisseur de ces services, il a mis en garde contre <strong>le danger de la position de monopole</strong>, qui peut facilement mener à un manque de partage des informations vis-à-vis des clients et partenaires, et à un refus d’amélioration de la qualité car «les gens n’ont pas le choix et doivent de toute façon utiliser nos services. “</p><p>Il a plutôt plaidé en faveur de solutions non dépendantes de la connaissance d’une poignée de personnes au sein de la structure qui détient le monopole, une plus grande souplesse en étant aussi transparent que possible envers leurs partenaires, et ce au moyen notamment d’une documentation précise des API, compte tenu de leurs exigences obligatoires pour assurer la sécurité du système. Une «documentation» très efficace qu’ils ont pu fournir pour expliquer comment extraire des données par le biais de leur service a été faite via la fourniture d’un outil plutôt qu’une spécification écrite: avec un ensemble d’entrées faciles à configurer par les utilisateurs, ces derniers peuvent extraire les données qu’ils souhaitent rapidement. Enfin, il nous a aussi rappelé que la qualité était difficile à définir, et qu’être capable d’«échouer rapidement» apportait des informations précieuses pour l’améliorer.</p><p>La sécurité c’est Notre métier</p><p>Mikko Hypponen, un expert en sécurité finlandais réputé, a présenté un exposé brillant qui nous a rappelé que la sécurité faisait partie intégrante de notre travail. Il a souligné que toutes les entreprises sans exception ont un aspect logiciel, car même sans créer de solutions informatisées, la plupart des données sont désormais stockées en ligne et vulnérables aux attaques de hackers.</p><p>Afin de nous démontrer l’importance à attacher à la sécurité, Mikko a pris à titre d’exemple quelques-unes des plus grandes «attaques» qui ont eu lieu ces dernières années, comme le piratage très récent en Décembre 2015 d’une centrale électrique en Ukraine (pour en savoir plus vous pouvez lire <a href="https://www.wired.com/2016/03/inside-cunning-unprecedented-hack-ukraines-power-grid/">cet article détaillé et très intéressant du magazine ‘Wired’</a>). Cette attaque a été rendue possible grâce à des réactions en apparence inodines de quelques opérateurs concernant une campagne de phishing qu’ils avaient reçu, contenant un document Word malveillant joint: ils avaient simplement cliqué sur un bouton pour activer le malware, exploitant une très ancienne vulnérabilité connue des solutions de bureautique Microsoft.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fk_uOdUYbIUA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dk_uOdUYbIUA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fk_uOdUYbIUA%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e2102ac09492702d5cb06246739c6431/href">https://medium.com/media/e2102ac09492702d5cb06246739c6431/href</a></iframe><p>Mikko a également expliqué que le milieu du piratage avait considérablement évolué, depuis l’acte d’individus isolés dans les années 90 jusqu’à la criminalité organisée en ligne de nos jours, en compétition pour le même ‘marché de la clientèle’. Vous avez sûrement dû entendre parler de leur oeuvre la plus connue, le ‘ransomware’, ce petit logiciel qui verrouille l’accès à vos données contre une rançon.</p><p>Pourquoi les ‘mauvais défis’ peuvent nuire à la qualité</p><p>Lloyd Roden du Royaume-Uni nous a présenté un «Top 10 des défis auxquels nous sommes confrontés aujourd’hui» dans le milieu de l’informatique en général: en commençant par une vidéo énergique rythmée par ‘eye-of-the-tiger’, il indique que les défis sont très différents selon les personnes, et a souligné le danger des ‘mauvais défis’ qui ont des effets négatifs sur nous, comme le ‘mauvais’ stress.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3bP6V4hWcs8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3bP6V4hWcs8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3bP6V4hWcs8%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0836a47f3a93d366ed4ad53bc96345c3/href">https://medium.com/media/0836a47f3a93d366ed4ad53bc96345c3/href</a></iframe><p>Au sein de ces défis dangereux trône l’interprétation erronée des métriques par la direction, ou comment bien souvent la quantité prend le dessus sur la qualité. En utilisant l’exemple du nombre de cas de test exécutés pour illustrer cette réalité: le testeur A exécute 30 cas de test par jour, le testeur B seulement 2. Par une interprétation erronée et un raccourci de l’esprit, le testeur A pourrait être considéré comme étant plus productif, pouvant mettre en péril la réputation du testeur B. Cependant, si nous commençons à remettre en cause ces mesures, et allons plus loin dans les détails, on pourrait s’apercevoir que A avait seulement 5 étapes par cas de test avec des pré-requis faciles et rapides à mettre en place, alors que B avait 40 étapes par cas de test avec de nombreuses données de test pré-requises et difficiles à créer à la main, sans aucune aide automatisée pour le faire.</p><p>Je me souviens personnellement, en complément du discours de M. Roden, de la présentation ‘Pass or Fail obsession’ de Rikard Edgren lors de la conférence Eurostar en 2012, où il mentionnait que la hiérarchie risquait de se concentrer beaucoup plus souvent sur les couleurs ‘vert’ ou ‘rouge’ représentant les 2 états possibles d’une suite de test à son exécution, plutôt que les résultats réels et la valeur de ce test, qui peuvent cacher un vice malgré le côté vert passant. Par résultats, je veux par exemple parler de nouvelles questions amenées suite à l’exécution, de problèmes observés dans les parties du logiciel qui ne sont pas couvertes par ce test spécifique.</p><p>Atelier ‘Tester les algorithmes intelligents: sommes-nous prêts?’:</p><p>Les présentations sont intéressantes mais on peut facilement se laisser porter et oublier que la meilleure façon d’apprendre vient avec la pratique: dans ce but, j’ai pu assister à l’atelier de Bill Matthew, dont le but était d’approcher le test d’algorithmes complexes que nous rencontrons fréquemment tous les jours.</p><p>L’un des exercices consistait à tester un système de recommandation.</p><p>Ce type de système se retrouve sur de nombreux sites web comme celui d’Amazon, qui recommande aux clients sur chaque page de produits d’autres produits, au même titre que le site internet d’une chaîne de télé peut vous recommander d’autres émissions à regarder en plus de celle qui vous intéresse réellement. Le degré d’éloignement des recommandations par rapport au produit qui vous intéresse au premier abord constitue un défi: la fonctionnalité de recommandation doit être construite de manière à éviter des ‘mauvaises’ recommandations; Il n’y a malheureusement aucune règle spécifique capable de déterminer cela, puisque dépendant de chaque utilisateur et donc très subjectif: par exemple si le système recommande de la nourriture contenant de la viande à un végétarien, cela peut être perçu de manière très négative, pouvant aller dans le pire des cas à la perte du client et une augmentation de la mauvaise réputation de l’entreprise.</p><p>En gardant ces aspects en tête, nous avons discuté en équipe des stratégies de test possibles. Une fois de plus, puisqu’il n’y a aucune règle spécifique avec ce type de fonctionnalité, il n’y a aucun comportement clair et prédéfini auquel s’attendre, et l’injection de deux jeux de données identiques en entrée avec les mêmes étapes peuvent conduire à des résultats très différents en sortie.</p><p>Voici quelques idées intéressantes qui ont émané des groupes:</p><ul><li>Afin de déterminer comment le système de recommandation se comporte, tester tout d’abord avec des jeux de données restreints et des étapes simplifiées pour observer les résultats: les recommandations peuvent se baser sur tant de critères — la couleur, la taille d’un vêtement — que les tests peuvent vite devenir complexes avec de nombreuses variables. Il faut donc pouvoir démarrer avec des tests simplifiés maîtrisés le mieux possible,</li><li>Accroître la diversité des données de test en réinjectant régulièrement les données de production, afin de recueillir plus d’informations et de couvrir plus de terrain,</li><li>Puisque le concept de ‘bonne’ ou ‘mauvaise’ recommandation est très subjectif, il peut être très utile d’établir différents profils de clients; L’analyse des données de production et des tests bêta par des utilisateurs réels permettront de répondre à ce besoin.</li></ul><p>Les résumés présentés ici ne reprennent que quelques présentations, il y en a eu bien sûr plein d’autres sur des sujets très variés, comme l’amélioration de la testabilité, ou encore la réduction des problèmes d’environnement. Pour plus d’informations consulter le programme complet de la conférence <a href="http://nordictestingdays.eu/schedule">ici</a>.</p><p><strong>Lightning talks ou ‘présentations éclair’: du contenu intéressant</strong></p><p>Pour ceux d’entre vous qui ne sont pas familiers avec ce concept, il s’agit d’une courte présentation informelle sans support visuel de cinq minutes maximum, suivie d’une discussion avec le public; Le but de ce format est d’encourager ceux qui n’ont jamais présenté un sujet sur scène à prendre la parole devant une audience. La session s’est tenue en début de soirée après quelques verres afin de rassurer les plus timides.</p><p>Du contenu très intéressant a émané de ces présentations éclair, plus ou moins liées à l’expérience personnelle, et amenées par de récentes réflexions. En voici quelques exemples:</p><p>Anticiper les anomalies en lisant le code</p><p>Avez-vous déjà eu ce moment où vous attendiez la livraison d’une nouvelle version du logiciel à tester car le code était en revue de pairs, et vous vous êtes demandés: “Qu’est-ce que je pourrais encore tester d’intéressant avant la livraison?”</p><p>Même si vous ne comprenez pas complètement le code écrit — que ce soit un langage que vous ne connaissez pas, ou que vous ne soyiez pas du tout familier avec la programmation objet -, il est toujours possible de repérer des schémas, des messages d’erreur codés en dur et des boucles de condition. Le participant a expliqué comment, en relisant les ‘pull request’ du code, il avait trouvé plusieurs cas qui n’avaient pas été gérés par le code pour les anomalies dont il attendait la correction, permettant ainsi d’éviter une livraison qui aurait échoué aux tests.</p><p>Quitter le test logiciel</p><p>Avez-vous déjà ressenti ce sentiment de nostalgie lorsque l’un de vos collègues vous annonçait qu’il ‘quittait’ son rôle de testeur pour prendre un nouveau poste? Il est possible que vous ayiez pensé à ce moment-là qu’il y avait de moins en moins de testeur car moins d’intérêt pour ces rôles… Et si cette nouvelle position leur permettait de répandre plus efficacement cette vision unique de la qualité qu’ils ont acquis au préalable? le participant a essayé de nous dire ici qu’endosser un nouveau rôle n’était pas nécessairement négatif pour le futur du test logiciel, et qu’au contraire avoir par exemple des développeurs ou des chefs de produit avec une expérience de testeur fonctionnel pouvait au contraire avoir plus de bénéfices et d’impact qu’il n’y paraissait.</p><p>La spécialisation vs la généralisation</p><p>Au cours de leur carrière, les testeurs acquièrent différentes compétences afin de pouvoir résoudre des problèmes pour tester les logiciels… Quelques-uns deviennent même spécialistes dans un domaine bien spécifique: automatisation, test des bases de données, tests de performance, etc. Le participant nous a fait ici réfléchir aux deux concepts: est-ce que se spécialiser revient à rétrécir son champ de vision et se biaiser? D’un autre côté, est-ce que l’on prend des risques à être perçu comme “pas suffisamment technique” si on n’est pas spécialisé pour ses futures perspectives de carrière? En nous rappelant que les deux idées sont compatibles puisque la spécialisation démarre toujours de la généralisation, il a comparé à d’autres métiers, par exemple être une infirmière au départ, qui se spécialise dans l’accompagnement et le traitement des patients atteints de cancer du poumon: votre noyau de compétences et votre objectif déviera peu.</p><p><strong>Pourquoi aller aussi loin pour une conférence?</strong></p><p>Il y a tellement de conférences en Europe de l’Ouest que vous pourriez vous demander pourquoi j’ai décidé de participer à cette conférence si loin de la France…</p><p>A cette question il y a une réponse bien précise: puisque je m’y suis rendu par mes propres moyens et qu’aucune entreprise ne me payait le ticket, j’y suis allé car j’ai été sélectionné en tant que participant pour présenter un sujet bien précis! Cétait donc une excellente opportunité de combiner l’apprentissage et le partage de connaissance avec d’autres testeurs.</p><p>Je publierai très bientôt un autre article, où vous en apprendrez plus sur cette conférence mais cette fois du point de vue ‘présentateur’.</p><p><strong>Pourquoi devrais-je participer à cette conférence?</strong></p><p>En 2012 à Amsterdam j’ai participé à la conférence Eurostar, qui a été la seule autre ‘grande’ conférence sur le test logiciel à laquelle j’ai pu assister. Nordic Testing Days est un peu loin si vous vivez en Europe de l’Ouest, et pourrait ressembler à d’autres, mais je l’ai personnellement beaucoup appréciée pour les raisons suivantes:</p><ul><li>Les organisateurs sont très accueillants, très arrangeants et très rassurants face aux quelques imprévus qui peuvent survenir;</li><li>Au travers de multiples jeux et activités proposées par les sponsors et les organisateurs, je me suis senti constamment impliqué et actif en-dehors des sessions de présentation: chasse au trésor, karaoké powerpoint, énigmes à résoudre, etc</li><li>Le plus important, de la bonne nourriture et des boissons gratuites, même pendant la soirée du jeudi, salutaire après une longue journée d’écoute et de présentation!</li><li>En tant que présentateur, je me suis senti estimé par l’organisation, et j’ai réellement eu l’impression d’apporter une contribution positive au public présent.</li></ul><p>Je dirais avant tout que cette conférence était moins formelle que par exemple Eurostar, qui par sa taille et sa réputation attire un plus grand nombre de sponsors et de professionnels.</p><p><strong>Résumé</strong></p><p>Sans aucune hésitation je recommande cette conférence non seulement aux testeurs mais plus généralement aux gens qui travaillent dans l’IT. Très bien structurée et organisée, tout en alliant le plaisir et le réseau, il s’agit d’une des conférences les moins formelles à laquelle assister avec pour autant un contenu incroyablement enrichissant et des présentateurs de qualité.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf815fe8ae4a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/conf%C3%A9rence-nordic-testing-days-2016-ma-vision-en-tant-que-participant-bf815fe8ae4a">Conférence Nordic Testing Days 2016 — Ma vision en tant que participant</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feedback from Nordic Testing Days conference — Audience perspective]]></title>
            <link>https://medium.com/lyon-testing/feedback-from-nordic-testing-days-conference-audience-perspective-e40fe469d9d9?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/e40fe469d9d9</guid>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Tue, 30 Aug 2016 08:38:32 GMT</pubDate>
            <atom:updated>2016-09-23T12:19:04.790Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Nordic Testing Days 2016" src="https://cdn-images-1.medium.com/max/198/0*9N0E65uV5yel2EYL.png" /></figure><p><em>Software testing conferences have spread up very quickly those last years. With nearly every country in Europe having its own, it can become difficult to make a choice when attending one.</em></p><p><em>After hearing a very good feedback from the Nordic Testing Days conference in Estonia from one of my previous managers, which compared it to a dozen of others, I decided to follow his recommendation: well, I was not disappointed at all. Let me present you here a summary of what happened.</em></p><p>It is 9 AM on Thursday, 2nd of June, in Tallinn, the capital of Estonia: the public is gathered in the biggest room and waits for the conference to start. The chairwoman comes up on stage, starts her speech, and within the next five minutes she makes a striking announcement: ‘We have plenty of food for the testers gathered here, because we don’t like hungry testers: they may start breaking software!”.</p><p>The audience laughs. The context and tone is set up. It sounds promising.</p><p><strong>Different audience</strong></p><p>Nordic Testing Days is interesting as it attracts a very different audience from the western Europe conferences: most testers are from the Baltic countries — which include Lithuania, Latvia and Estonia — and from the Scandinavian countries. It is an excellent opportunity to meet new faces and broaden the social network, as well as approaching testing from completely different perspectives since some of the keynotes and talks were focused on those people’s experience.</p><p>There is also what I call the usual crew from the United Kingdom, which includes testers who are accustomed to speaking at the various conferences around Europe: I can name for example Bill Matthews, Dan Billing and Stephen Janaway.</p><p><strong>What came out of the talks?</strong></p><p>Monopoly should not prevent quality</p><p>Estonia is nicknamed <strong>“e-Estonia”</strong> as it describes the country’s emergence as one of the most advanced e-societies in the world. The keynote introducing the conference highlighted that: it was presented by Andres Kütt, a digital architect working for the Estonian government, who is collaborating in providing e-services for the vital sectors to interconnect with, such as healthcare, or law institutions. This obviously infers that you have to consider those sectors perspective in order to provide the most useful solutions.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeqTvXuMLClw%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeqTvXuMLClw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeqTvXuMLClw%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1866e8dd7ab35a0fbfb43af470724687/href">https://medium.com/media/1866e8dd7ab35a0fbfb43af470724687/href</a></iframe><p>Andres insisted on considering, when looking for improving quality, not only the services they were providing, but the whole ecosystem using it: the users, the sectors, the different requirements. As being the only provider for such services, he warned about the <strong>dangerous monopoly way of thinking</strong>, which includes the easy drifting towards a lock-in attitude and the denial of quality improvement regarding their solutions, because as he said “people don’t have the choice, they have to use it anyway”.</p><p>Instead of that, he advocated for reducing dependency, increasing flexibility by being as transparent as possible towards their subsidiaries: documenting APIs, considering their mandatory requirements to insure system safety. A very efficient ‘documentation’ that they can provide in order to explain how to extract data through their service was done via the delivery of a tool rather than written specification: with a set of easy input configured by the users, the latter can extract the data they want fast. Finally, he also reminded us that quality was hard to define, and being able to ‘fail fast’ helped a lot in getting valuable feedback to improve it.</p><p>Security is your job</p><p>Mikko Hypponen, a very well-known and reputated security expert, presented a brilliant talk that resulted in reminding us that security was absolutely part of our job. He highlighted that all companies were software one, whether they provide software solutions or not, since all the data nowadays is digitalised and available online.</p><p>To demonstrate how important it was for us to be aware of security, he took as an example some of the biggest ‘attacks’ that occurred, such as the hack of Ukraines power grid link in December 2015 (for more info you can read <a href="https://www.wired.com/2016/03/inside-cunning-unprecedented-hack-ukraines-power-grid/">this very interesting and detailed article</a> from Wired). This attack was initially made possible through the reactions of few operators regarding a phishing campaign they had received, containing a malicious Word document attached: they ‘simply clicked on a button’ to enable the malware, exploiting an old-school vulnerability from Microsoft solutions.</p><p>Mikko also explained that the state of hacking evolved from random individuals in the 90’s to online organised crime nowadays, competing for the same ‘customer market’.</p><p>Why ‘Bad challenges’ in testing are dangerous</p><p>Lloyd Roden from the United Kingdom presented us his talk about the “Top 10 testing challenges that we face today”: starting with an energising eye-of-the-tiger soundtrack video showing that challenges are very different and relative to each one of us, he highlighted the danger of ‘bad’ challenges which led to negative effects on us included bad stress.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3bP6V4hWcs8%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3bP6V4hWcs8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3bP6V4hWcs8%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0836a47f3a93d366ed4ad53bc96345c3/href">https://medium.com/media/0836a47f3a93d366ed4ad53bc96345c3/href</a></iframe><p>Within those dangerous challenges lied the incorrect interpretation of metrics by management, or how quantity very often took over quality. Using the example of test case execution count to illustrate that reality: tester A executes 30 test cases per day, tester B only 2. As an incorrect interpretation and shortcut of the mind, tester A could be considered as being more productive, therefore jeopardizing tester B reputation. Now, if we start questioning those metrics, and going more into details, we may find out in fact that tester A had only 5-steps test case with easy and fast pre-requisites to set up, whereas tester B had 40-steps test case with lots of test data to prepare for each test, with no easy automated way to do it.</p><p>I personnally remember, to backup M. Roden’s talk, the ‘Pass or Fail obsession’ track talk from Rikard Edgren at a previous session of Eurostar in 2012, where the management often focused much more on the overview of ‘Green or red’ color of test execution, rather than the outcomes of the tests, even if they were shown as ‘green’. By outcomes, I mean new questions, issues seen in areas of the software which were not covered by that specific test, etc.</p><p>Workshop ‘Testing smart algorithms’:</p><p>Track talks are good but we can easily forget that the best ways to learn come with practice: the conference workshops were made for that purpose, and I was able to attend Bill Matthew’s one, whose goal was to approach testing for those complex algorithms which we frequently come across in our daily lives.</p><p>One of the exercices used for that workshop was about testing a recommendation system.</p><p>Those systems can be seen on many websites, such as Amazon recommending its customers more articles to buy, or a TV channel suggesting other TV shows to watch, which may — or may not — be similar to the one you previously watched. The — may not — is part of the challenge when you’re building that type of feature, since you may do a ‘bad’ or a ‘good’ recommendation; Unfortunately, there is no specific rule to predict that, since it strongly depends on how customers interpret it: for example, recommending meat food to a vegetarian customer can be perceived as a bad recommendation.</p><p>With that in mind, we gathered in teams of five to elaborate and discuss possible testing strategies. The difficulty, again with that type of functionality, is that there is no specific rule, which means, there is no defined and clear behaviour to expect, and injecting two identicals sets of same data into the same test with the same steps may lead to a completely different outcome.</p><p>Interesting ideas came out of the discussion, including:</p><ul><li>In order to determine how the recommendation system behaves, test with very small sets of data and use the same steps for different sets to observe the outcome: the recommendation system may work from various criteria for each article, such as colour, size, etc, and the high number of variables makes it too hard to understand the behaviour with complex tests,</li><li>Growing the sets of data with the sets generated in production environment by real customers, in order to reinject it in the test environment and gather more information,</li><li>Since ‘bad’ and ‘good’ recommendations are very subjective, it may be a good idea to determine various customer profiles; You could do that by collecting and analysing plenty of data, or through beta testing.</li></ul><p>Those were some of the main keynotes and workshops, but there were plenty of others focused on various topics, such as improving testability, or easying up the environmental issues. You can view the detailed program <a href="http://nordictestingdays.eu/schedule">here</a>.</p><p><strong>Lightning talks: interesting content by newcomers</strong></p><p>For those amongst you who are not familiar with that concept, it is a 5-minutes talk format followed by a short discussion which aims at encouraging non-speakers to go ‘on stage’ in front of an audience. The session was held in the evening after everyone has had a few drinks to relax, probably to keep it informal and reassure the shyest participants.</p><p>Very interesting content also came out of those talks, which were either related to a brief bit of personal experience, either brought up by recent thoughts and reflexion. Here are few examples of the topics covered:</p><p>Anticipate bugs by reading code</p><p>Have you had a moment when you were waiting for a new software version delivery, and you were wondering what else you could do in order to do more testing beforehand? Even if you don’t understand the code written — specific development language you don’t know about, or you are not familiar with development –, it is still very easy to spot for example the ‘if’ conditions and the user error messages written. The participant explained he had found several cases which had not been dealt with by just looking at those, preventing a delivery which consequently would not have passed the tests.</p><p>Leaving testing</p><p>Have you already had this weird feeling when one of your fellow tester colleagues announced he was ‘leaving’ his tester position to try on a new role? You may have felt that testing positions are disappearing and people are considering them less and less… unless their unique vision towards quality that they acquired as a tester can be spread in a more efficient way at a different position? The participant here tried to tell us that it is not necessarily negative for the future of testing that people go on and try other roles, and that reinforcing collaboration with developers, product owners with a testing background may have more benefits and positive impacts than it seems at first.</p><p>Specialisation versus generalization</p><p>Testers may have to acquire so many different skills across their career in order to solve problems and be able to test softwares… Some of them even become specialists in a specific domain: automation, database testing, performance, etc. The participant gave us food for thoughts by challenging both concepts: Are you not narrowing your focus and biasing yourself if you become too much of a specialist? On the other hand, are you not risking to be seen as not technical enough if you don’t have any speciality, jeopardizing future job positions? Reminding us however that generality and speciality are still compatible since the latter always derives from a general core concept, he compared to other jobs, such as being a nurse — general skill — versus being a nurse specialised in attending people having lung cancers: your core skill and objective does not change.</p><p><strong>Why going so far away for a testing conference?</strong></p><p>There are so many testing conferences in western Europe that you may wonder why I decided to attend a conference so far away from France…</p><p>In fact, since no company was sponsoring my tickets, there is only one reason: I was selected as a speaker! It was therefore an excellent opportunity to combine learning and sharing knowledge with other testers.</p><p>I will very soon publish another article where you will learn about this conference from a completely different angle, which is the speaker perspective, so stay posted ;)</p><p><strong>Why should you attend this conference?</strong></p><p>In 2012 in Amsterdam I attended Eurostar software testing, which was the only other ‘big’ software testing conference I have ever attended. Nordic Testing Days may be a bit far away to attend if you are living in Western Europe, and may look similar to others, but I have personally had a much better feeling about it, here is why:</p><ul><li>The organisers were very helpful, well organised and arranging with issues that may occur;</li><li>Through various games and sponsors activities, I constantly felt active and entertained even outside of the talks: treasure hunt, powerpoint karaoke, sponsor puzzles, etc</li><li>Good food and free drinks, even during the party on Thursday evening, that is important after a long day of attention!</li><li>As a speaker — I will come back to it in another article –, I felt very valued through the organisation of my talk, and really felt I was bringing a positive contribution.</li></ul><p>Overall I would say this conference was less formal than for example Eurostar, which obviously by its size attracts a bigger range of sponsors and professionals.</p><p><strong>Summary</strong></p><p>Without any doubt I would recommend this conference to other people working in IT, whether they are testers or not. Very well structured and organised, keeping it fun and social, one of the least formal conferences to attend with such rich content and famous professionals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e40fe469d9d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/feedback-from-nordic-testing-days-conference-audience-perspective-e40fe469d9d9">Feedback from Nordic Testing Days conference — Audience perspective</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Du bon usage des User Story et Epic]]></title>
            <link>https://medium.com/lyon-testing/du-bon-usage-des-user-story-et-epic-e98370ea7a25?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/e98370ea7a25</guid>
            <category><![CDATA[agilité]]></category>
            <category><![CDATA[processus]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Mon, 29 Aug 2016 15:04:29 GMT</pubDate>
            <atom:updated>2016-09-23T12:19:01.685Z</atom:updated>
            <content:encoded><![CDATA[<h3>Définition d’une User Story</h3><p>Les spécifications sont souvent une cause majeure de l’échec d’un projet. De mauvaises spécifications peuvent entraîner un manque de vision sur le produit attendu, des fonctionnalités redondantes/contradictoires.</p><p>Le but de l’utilisation des « user stories » est de permettre de répondre plus rapidement et avec moins de coût au changement rapide des exigences du monde réel.</p><p>En méthode agile, la US est écrite pour partager la vision développeur/testeur/projet à travers des revues fréquentes et non formelles en même temps que celles-ci sont rédigées/modifiées.<br>On retrouve ce partage également dans les cycles en V au travers de la notion des revues d’exigences/spéc très formelle après que celle-ci soit rédigée (moins d’A/R mais processus très figé — pas de modification en direct).<br>Les « user stories » décrivent les fonctionnalités qui seront utiles. Les « user stories » sont composées de trois aspects (principe des 3C):</p><ul><li><strong>Carte</strong> : Support décrivant la story</li><li>Exigence (description)</li><li>Priorité</li><li>Temps de dev/test</li><li>Critère d’acceptance</li><li><strong>Conversation</strong> : Échanges sur la « user story » qui servira à étoffer les détails (Testeur/PO/Devs). Cette phase commence pendant la phase de planification de la release et continuera quand la User Story sera planifiée (mind-mapping/brainstorming)</li><li><strong>Confirmation</strong>: Les tests qui véhiculent et documentent les détails et seront utilisés pour déterminer quand une « user story » est terminée. Ces tests fonctionnelles/non fonctionnelles devront être montrés et suivi à travers le temps afin de satisfaire la US et être considérée comme « Done »<br>[Mike Cohn : User Stories appliquée. 2009] [REQB® Certified Professional for Requirements Engineering Niveau Fondation]</li></ul><h3>Méthode Invest</h3><p>Quelles sont les caractéristiques d’une bonne story ? L’acronyme INVEST est un bon moyen de réponse.</p><ul><li>I — Independent (<strong>I</strong>ndépendante des autres)</li><li>N — Negotiable (<strong>N</strong>égociable initialement, plutôt qu’un engagement ferme)</li><li>V — Valuable (Ayant de la <strong><em>V</em></strong><em>a</em>leur en soit)</li><li>E — Estimable (<strong>E</strong>valuée en termes de complexité)</li><li>S — Small (<strong>S</strong>uffisamment petite)</li><li>T — Testable (<strong>T</strong>estable en principe, ce qu’on vérifie en écrivant un test)</li></ul><h4>Plus en détail</h4><p><strong>Independante<br></strong>Une story se doit d’être indépendante. De cette façon il doit être possible de planifier n’importe quelle story et de l’implémenter dans le système dans l’ordre que l’on veut. Cette indépendance permet également lors de test de retirer des storys défaillantes de la release.</p><p><strong>Négociable… et Négociée<br></strong>Une bonne US doit dans un premier temps ne pas contenir d’élément technique étouffant la story, on se limitera à l’essentiel lors de la définition de la release (macro chiffrage). Ces éléments seront ajoutés par la suite lors des échanges entre les testeurs/développeurs et le rédacteur de la story.</p><p><strong>Avec de la Valeur<br></strong>Une US se doit d’avoir une valeur pour l’utilisateur final. Exemple : la refactorisation de code n’est pas quelque chose de pertinent d’un point de vue utilisateur. Lors d’évolution majeur, il arrive souvent que l’équipe développement décide d’entièrement prendre de l’avance sur des tâches techniques (sur l’ensemble du projet) au lieu de se concentrer que sur la partie voulue par l’utilisateur. Il vaut mieux ne livrer qu’une partie du projet de façon régulière que de prendre du retard sur des tâches techniques n’affectant par l’utilisateur final (projet vertical)</p><p><strong>Estimable<br></strong>Une bonne US doit être évalué (complexité). Afin de répondre à ce point, les critères d’acceptations devront être précis et compris par l’ensemble des équipes. De plus la US ne devra pas être trop grosse (1 US ne doit définir à elle seul un projet)</p><p><strong>Taille S (Small)<br></strong>Une bonne US ne doit pas dépassé quelques jours-hommes. Sinon il faut la splitter en plus plusieurs story et la story initial devenant une EPIC.</p><p><strong>Testable<br></strong>Une bonne US est testable. Il faut que la description et critères d’acceptante de celle-ci soit suffisamment pertinent pour ne pas laisser d’ambiguïté lors des tests. C’est une des critères les plus importants d’une story.</p><h3>Définition d’une EPIC</h3><p>Une Epic correspond à une macro fonctionnalité du système à développer. Elle englobe de ce fait un ensemble de User Stories qui seront rattachées à l’EPIC.</p><p>On retrouve souvent l’EPIC dès le début d’un projet; à ce stade la fonctionnalité n’est pas du tout détaillée ni priorisée. C’est au fur et à mesure que la fonctionnalité sera spécifiée que l’Epic va être complétée par l’ajout/suppression de User Story. De par le découpage en US, le développement d’une EPIC se fera en plusieurs versions (ou sprints).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e98370ea7a25" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/du-bon-usage-des-user-story-et-epic-e98370ea7a25">Du bon usage des User Story et Epic</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[User Story and Epic. What is it?]]></title>
            <link>https://medium.com/lyon-testing/user-story-and-epic-what-is-it-10184b10483?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/10184b10483</guid>
            <category><![CDATA[agility]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Mon, 29 Aug 2016 15:04:26 GMT</pubDate>
            <atom:updated>2016-09-23T12:19:00.632Z</atom:updated>
            <content:encoded><![CDATA[<h3>Definition of User Story</h3><p>The specifications are often a big cause of failure in projects. Bad specifications could lead to misunderstandings about the final product, wrong functionalities, and not required features.</p><p>The objective of “User stories” is to respond quickly and with less cost to modifications of requirements (new user needs for example).</p><p>With agile methodologies, the US is written to share the vision of developers/testers/project leaders instead of continually reviewing during the redaction phases.<br>We find this sharing also in the V cycle through the very formal notion of requirements reviews after this one is drafted (less + but very motionless process — no live modification).<br>The “ user stories “ describe the features that will be useful. The “ user stories “ consist of three aspects ( principle of 3C) :</p><ul><li><strong>Card</strong> : Support describing the story</li><li>Requirement ( description)</li><li>Priority</li><li>Planning development/ testing</li><li>Acceptance criteria</li><li><strong>Conversation</strong> : Discussion on “ user story “ that add the details ( Tester/PO/Devs ) . This phase begins during the release planning phase and will continue when the User Story will be planned ( mind-mapping / brainstorming)</li><li><strong>Confirmation</strong>: Tests that convey and document details and will be used to determine when a “ user story “ is ready to test. These functional/non-functional test will be demoed and followed over time to meet the US and then considered “ Done”<br>[ Mike Cohn : User Stories Applied . 2009] [ REQB® Certified Professional for Requirements Engineering Foundation Level ]</li></ul><h3>Method Invest</h3><p>What are the characteristics of a good user story? Invest method is a good answer</p><ul><li>I — Independent (<strong>I</strong>ndependent of other User Story at release)</li><li>N — Negotiable (<strong>N</strong>egotiable initially, rather than a firm commitment)</li><li>V — Valuable (Having some <strong>V</strong>alue )</li><li>E — Estimable (<strong>E</strong>stimable regarding complexity)</li><li>S — Small (Enough <strong>S</strong>mall)</li><li>T — Testable (what we verify by writing a <strong>T</strong>est)</li></ul><h4>More in detail</h4><p><strong>Independent<br></strong>A User Story must be independent. It should be possible to plan any user story and implement the system in the order you want . This independence also allows testing in removing failed stories of the release.</p><p><strong>Negotiable… and Negotiated<br></strong>A User Story should initially contain no technical element stifling the story will be limited to the essential in defining the release (macro costing). These elements will be added later during exchanges between testers/developers and the writer of the story.</p><p><strong>Valuable<br></strong>A User Story must have a value for the end user.<br>Example: the code of factorisation is not something relevant from a user perspective. When major changes, it often happens that the development team decides to completely take the lead on technical tasks (of the entire project) instead of focusing only on what is required by the user. It is better to deliver a part of the project but regularly as falling behind on technical tasks affecting the final user (vertical project)</p><p><strong>Estimable<br></strong>A User Story must be evaluated (complexity). To answer this, the acceptance criteria must be clear and understood by all the team. Moreover the User Story should not be too big (1 User Story shouldn’t define a whole project — role of a Epic)</p><p><strong>Small<br></strong>A User Story should not exceed a few man/days. Otherwise, it should be separated in several stories then original story becomes an Epic.</p><p><strong>Testable<br></strong>A User Story is testable. We need the explicit description and criteria, it to be relevant enough to leave no ambiguity in testing. This is one of the most important criteria of a story.</p><h3>Definition of EPIC</h3><p>An Epic corresponds to a macro functionality of the system to develop. It includes therefore a set of User Stories that will be linked to the Epic .</p><p>An Epic is created from the very beginning of a project.<br>At this time the functionality is not detailed nor prioritised.<br>The feature will be specified gradually and the Epic completed with addition/deletion of User Story. The development of EPIC will cover several versions (or sprints) .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10184b10483" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/user-story-and-epic-what-is-it-10184b10483">User Story and Epic. What is it?</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bug magnet, un outil d’aide aux tests]]></title>
            <link>https://medium.com/lyon-testing/bug-magnet-un-outil-daide-aux-tests-8946013d1a1f?source=rss-1ac9792d7922------2</link>
            <guid isPermaLink="false">https://medium.com/p/8946013d1a1f</guid>
            <category><![CDATA[outil]]></category>
            <category><![CDATA[plugins]]></category>
            <dc:creator><![CDATA[Lyon Testing]]></dc:creator>
            <pubDate>Sat, 06 Aug 2016 12:16:22 GMT</pubDate>
            <atom:updated>2016-09-23T12:19:15.992Z</atom:updated>
            <content:encoded><![CDATA[<p>Permettez-moi de vous présenter un outil que je trouve vraiment pratique. En tant que testeur, vous aimez utiliser des heuristiques pour tous les types de données que vous devez remplir. Prenons un exemple simple, un formulaire où vous devez entrer un nom, une adresse et un texte.</p><p>Vous allez tester avec des champs vides, un texte très long, des injection SQL ou JS, des caractères spéciaux, des caractères de fin de ligne, un texte là où un nombre est requis et probablement aussi avec plusieurs encodages, etc (voir cette page <a href="http://testobsessed.com/wp-content/uploads/2011/04/testheuristicscheatsheetv1.pdf">heuristique Cheat Sheet </a>pour plus d’idées). Si vous ne disposez pas de tests automatiques d’interface permettant de tester ceci avec des données, alors vous avez besoin de remplir ces champs “manuellement”, ou vous pouvez vous faire aider d’un outil comme “<a href="http://gojko.github.io/%20bugmagnet%20/">Bug Magnet</a>” disponible dans le magasin Chrome.</p><p>Ensuite, il suffit d’un clic droit, et vous serez en mesure d’ajouter</p><ul><li>du texte avec des codages différents (latin, cyrillique, arabe, …) ou un mélange utilisant un Lorem ipsum</li><li>des chaînes de caractères très longues (jusqu’à 64K)</li><li>des noms usuels, des adresses et des villes de différents pays</li><li>des adresses e-mail et URL valides et invalides</li><li>des nombres (numériques, exponentiels,…etc)</li><li>différents types de chaînes vides avec des espacements, des espaces de tabulation, des retours à la ligne…</li><li>et aussi des injections SQL, javascript …</li></ul><figure><img alt="LoremIpsum" src="https://cdn-images-1.medium.com/max/150/0*a5RgLWJA28as2zDQ.png" /></figure><figure><img alt="LongNames" src="https://cdn-images-1.medium.com/max/150/0*OxHx6IAFl_5g026J.png" /></figure><p>C’est l’outil parfait pour le testeur paresseux afin d’accéder aux cas extrêmes pour les tests exploratoires. Bien sûr, cela ne constitue pas une liste exhaustive et vous devrez toujours utiliser votre créativité. De plus, vous pouvez facilement étendre les options disponibles avec vos propres fichiers de configuration (voir ce fichier <a href="https://github.com/gojko/bugmagnet/blob/master/template/common/config.json">JSON</a> par exemple)</p><h4>Revue du Plug-in</h4><h4>Plus</h4><ul><li>Gratuit et open source (disponible sur <a href="https://github.com/gojko/bugmagnet">github </a>)</li><li>Rapide à ajouter et utiliser</li><li>Peut être étendu avec des fichiers JSON</li><li>Disponible pour Firefox et Chrome</li></ul><h4>Moins</h4><ul><li>Non disponible pour certains champs, on a parfois besoin d’entrer un caractère, puis clic droit à nouveau (<a href="https://github.com/gojko/bugmagnet/issues/13">Bugs</a>!)</li></ul><figure><img alt="approved.eps" src="https://cdn-images-1.medium.com/max/150/0*eJv5sg0EsugtHBaO.jpg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8946013d1a1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lyon-testing/bug-magnet-un-outil-daide-aux-tests-8946013d1a1f">Bug magnet, un outil d’aide aux tests</a> was originally published in <a href="https://medium.com/lyon-testing">Blog articles</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>