Lyon Testinghttps://www.lyontesting.fr
Fri, 27 Jul 2018 09:01:00 +0000en-GBhourly1https://wordpress.org/?v=4.9.8https://www.lyontesting.fr/wp-content/uploads/2017/01/test-1-150x150.pngLyon Testinghttps://www.lyontesting.fr
3232Our reading recommendations of the week #30 – 2018https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-30-2018/
https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-30-2018/#respondFri, 27 Jul 2018 08:59:22 +0000https://www.lyontesting.fr/?p=2803 Read More Read More]]>Here we go with our reading recommendations of this 30th week of this year. Be it on the beach, in the mountains or while fighting a mosquito in a tent, there’s no break for learning and sharing thanks to awesome people around the world writing blog articles. This week, we’ll cover the following subjects:

Maybe that asking yourself “What tests to automate?” is not the right question

The software Testing anti-patterns

The importance of Design QA

We are often asked to find a strategy for automatic check. What is best to automate? Boring tests? Tests that are often repeated? Your regression test plan?

Finally, finding inconsistencies in digital product design should not be neglected. Adding features is a thing, but quality also means it needs to be well designed and consistent with the rest of the product, and no design debt should never be added at any time. Please read this article introducing Design QA written by Jess Eddy.

See you in a few weeks for other reading recommendations. Meanwhile, enjoy the summer!

]]>https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-30-2018/feed/0Our reading recommendations of the week #28 – 2018https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-28-2018/
https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-28-2018/#commentsMon, 16 Jul 2018 16:03:07 +0000https://www.lyontesting.fr/?p=2785 Read More Read More]]>Welcome to our reading recommendations of this week, you will read the following articles :

What is A/B Testing about?

Participating in code reviews as a tester

Crafting user stories that agile teams will love

A/B testing is a very special type of test. It carries a test name and uses simple methods: when used in the right way, it can get very relevant outcomes. I invite you to discover it in the article “What is A/B Testing About?” written by Maaret Pyhäjärvi

Code reviews are too often reserved for developers only. Chris Kenst suggest ideas in order for testers to finally be able to integrate this activity and strenghten the tester/developer collaboration. Read this article.

To finish, a bit of theory with the good construction of the US so that users finally love this type of abstract language.Nishi Grover sticks to the exercise in this article.

Thank you for your attention, and see you in two weeks!

]]>https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-28-2018/feed/1Our reading recommendations of the week #26 – 2018https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-26-2018/
https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-26-2018/#respondThu, 28 Jun 2018 08:07:18 +0000https://www.lyontesting.fr/?p=2766 Read More Read More]]>Welcome to our reading recommendations of this week, you will read the following articles :

“Sometimes as testers in an agile environment we want to jump in and get straight to teaching people when instead we should sit back and feed the team”. This first article, “A starving man can not learn to fish“, gives us food for thoughts about this objective that we may want to rush.

Are you still wondering what the hell is Docker and how it can help you with your day-to-day testing life ? Quality Spectrum tries to explain in the simplest way “What is Docker“.

Finally, a bit of technique : “Introduction to SQL injection” written by Kristin Jackvony. I strongly recommend to read her Google page where she gives many quick and easy technical tutorials for test tools that we often use. If you are afraid of the word ‘POST’ in your testing job because it sounds ‘too’ technical for you, that page is perfect to get your fears away!

Thank you for your attention, and see you in two weeks !

]]>https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-26-2018/feed/0Our reading recommendations of the week #22 – 2018https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-22-2018/
https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-22-2018/#respondThu, 31 May 2018 18:43:01 +0000https://www.lyontesting.fr/?p=2745 Read More Read More]]>Welcome to our weekly reading recommendations! This week you will read about the following topics:

Most Common Mistakes During the Transition to Agile

How to use Moments within Postman

Dockerized testing vs end-to-end testing

First a long list of common mistakes an Agile coach often sees in companies failing to adopt Agile. It seems so easy to “be Agile”, but if you ignore the quality factor or have a poor team structure unable to act as a truly cross-functional team (to only cite a few), then success is far from being guaranteed. The post written by David Tzemach comes in 2 parts: part 1 and part 2.

Several months ago I did osteopathy with a specialist who was blind; While patting on my back and moving around some vertebrae of mine, he explained me how he used iOS screen reader functionality to be able to get on with his banking applications. The article Blind customers locked out by bank web upgrades released recently by the BBC reminded me of the problematics that disabled people can meet with technology when accessibility is underlooked. A very empathic read!

Recruitment process may lead to disappointment since candidates spend a few hours within a formal context and meeting few people they may even not work along with. To decrease this risk, the company QualityMinds establishes the “Meet The Minds Day“, a full day of integrating the candidate into the former’s daily life. Have a read, it may inspire you to find your own pearls!

Finally, a clean code allows to make clean tests. A minimum of feedback/bug allows the tester to spend more time doing exploratory testing and asking questions. Samer Buna relates this story in this article.

Elon Musk telling us that relying too much on automation was a mistake

A tester skill: response to change

Agnostic testing

Elon Musk said a few days ago that “Excessive automation at Tesla was a mistake…Humans are underrated” in a tweet after a CBS interview. Of course, as Rosie Sherry reminds us in this short post Too much automation you say Elon Musk? these words resonate in our tester brains always trying to find the correct balance between “Human testing” and “Robot testing”. Thanks for reminding us that humans are still essentials.

Finally, in a world of continuous delivery, because release happens regardless of your testing activity, Anne-Marie Charrett starts thinking on how focusing on enabling quality testing to happen in this specific development pace. It was 10 years ago, but focused on improving testing we sometimes forget to ask the question “where is the risk?”: Agnostic testing – Do you believe? by Anne-Marie Charrett.

For the first time being at my company I will be entering the dragon’s den, full of precious gems for our software but also hiding traps and slipping paths… going on-site to meet one of our customers!

While I am preparing that meeting in order to be able to take out valuable test scenarios, I came across this interesting article from Katrine Kavli, “What is a test persona?“. It gives a concise insight on the minimum information required to draw such a character for your application testing.

In your lifetime you must have heard at least once about the joke: “A [whatever name you may find] walks into a bar…”. I sometimes use this joke in improvisation theater where we tend to replace the [whatever name you may find] by any name which comes immediately in mind. László Szegedi decided to reuse that joke in the context of software testing: “A tester walks into a bar: reviewing test techniques“. I found it a refreshing and original way of going through known test methods that we often apply.

Finally, an audio recommendation with the interview of Michael Bolton by Joe Colantonio explaining Rapid Software Testing, a methodology and mindset for testing software expertly and credibly in uncertain conditions and under extreme time pressure. Listen to it if you want to know how to perform the fastest, least expensive testing you can while still completely fulfilling the mission of testing.

That’s it for this week folks! See you in two weeks time!

]]>https://www.lyontesting.fr/en/our-reading-recommendations-of-the-week-14-2018/feed/0A tester Interview #5 – Yann Personhttps://www.lyontesting.fr/en/a-tester-interview-5-yann-person/
https://www.lyontesting.fr/en/a-tester-interview-5-yann-person/#respondThu, 29 Mar 2018 08:00:25 +0000https://www.lyontesting.fr/?p=2577 Read More Read More]]>Following Julien, Thierry, Stéphanie and Maria, it is now up to Yann Person – who came to give a presentation on Live Functional Monitoring in Last November 2017 -, to answer our Questions&Answers in this fifth episode.

Who are you, what are you doing, where are you working?

Yann Person, 28, I’m Lead QA for Manomano: basically I make sure that what our developers build behaves as expected by our product team. Previously, I worked for fintech companies: Younited Credit and Leetchi/MANGOPAY.

How would you describe your work to a 6-year-old?

Take a car: in order for it to run you need 4 wheels, an engine, a steering wheel and so on. My job is to check that all needed elements are present, up and running.

Looking back, and if you were to start again as a tester, what advice would you give?

Be even more curious: ask people in the testing field how they work, what they do on a daily basis, go to more Meetups. The more you communicate, the more you learn.

If you were to recruit a tester, what would you look for in a candidate for this role?

I do recruit testers. What do I look for? Curiosity and eagerness to learn. If these two skills are present, it’s a very good start By the way, if you read this and are looking for an opportunity, tweet me @troblous.

Tell us an anecdote of your life as a tester (good or bad time, incredibly hard bug to reproduce or analyse …)

Concurrency. We knew an issue occurred in situations where several payment transactions happened at the same time. It took several tries with specific tools to reproduce the issue. Once we reproduced it, we knew it was done. We didn’t know how to fix it at the time but that wasn’t something we were worried about. The only thing that mattered was that we eventually reproduced the issue.

What drives you crazy in the common misconceptions about testing?

A lot of people see testing as a center of cost and something that should just be handled after development. It simply is untrue. Testers, developers and product managers are all pieces of a bigger puzzle: without one of them, you cannot finish it!

What challenges do you face as a tester in a software product team? And how do you overcome them?

Communication is key. You’re in between Product, Support and IT teams. You need to be able to quickly adapt your element of languages and be reactive when needed. I try to listen a lot and understand where we’re gonna have pain points so that we can address them as early as possible.

One of the challenges you have faced in testing a particular feature

One example is a scoring engine we had: numerous inputs that led to an incredible number of scenario. Stuff like this isn’t manually testable, and can be difficult to automate on a high level. Although, as it was a standalone service that ran on its own, Gherkin language could be a very good idea to describe example scenario. And that’s how we added dozens of different tests that were able to properly go through the different possibilities that the engine offered.

Do you have models, people inspiring you (testers or not)?

Honestly, any entrepreneur. They face difficulties all the time, overcome them and they end up building extraordinary companies.

How do you keep learning?

I read a lot of blogs and as much as possible I discuss with peers from the industry. That’s how you can learn real life examples of tricky tests implementations for example.

Cite one or more tools that have become essential to you?

Runscope (API), GhostInspector (web), JMeter (load/perf). There are of course other tools, but these ones are the most important in my toolbox.

What revolution should the testers be prepared for?

I think the next big challenges will be related to AI and neuronal networks.
As of today, most of the software products we have are simple: when you input A, you get B. But with AI, you can’t really know what the system is going to return meaning you don’t really know how to test the output.
The next 5/10 years will be very interesting.

Thank you very much Yann. Do not hesitate to comment if you want to continue the debate on one of the subjects. We will have another guest soon.

This time read about the following topics:
– Becoming rich with Spotify without being a musician
– Signing off on a release: is it the tester responsibility?
– An AI trying to catch bugs before devs make them

Then, let’s talk about signing off on a release, Michael Bolton explains that testers should never do that. The decision being a business decision, not a technical one. Read how to deal with that if you are asked to decide to ship or not: Signing off.