Here are our reading recommendations of the week #19. We are first suggesting 2 articles around a recurrent subject: automatic checking and how to deal with flaky tests. Then a feedback about how challenging it is to be a software tester in a Continuous Deployment environment. Finally, the last article is an analogy with restaurants that intend to help testers introducing themselves to developers.
Testing an open source project has some advantages compared to proprietary softwares:
- everything is public and can be shared with anyone interested
- you can communicate about your project, issues and features with no fear
- you can use tools that are free only for open source projects (like Atlassian suite, Saucelabs…)
- you may be helped by contributors and benefit from the community of open source lovers
Here’s our list of reading recommendations for these 2 last weeks.
We are full of cognitive biases and you might be aware of this fact if you read our blog. HDD or Hype-Driven Development happens when a development team tends to be driven in her choices only by novelty and buzzwords; only selecting technologies that seems to be trending. An overview article is available here.
Please allow us to first wish you a very happy new year. May year 2017 be a year of all success, new learning about Software Testing, and maybe new challenges. Who knows what will be the future of testing? Software dev and test in 2017, what’s next?
New year always comes with good resolutions too.
Mobile phones are everywhere and almost every service in the world has its own application. If not, the website is responsive and can be used on a small screen with bad network, and not only on your desktop with a fiber network. As a tester of a website or an Android/iPhone/WinPhone application, you need to test it as a real user, meaning on one or more smartphones or at least on the most used by your users/customers. It includes manual and automatic testing though. What if you don’t have one billion €uros/$ollars/£ounds to buy all the smartphones needed to be tested? Will you rely on Chrome dev tools for browsers application, knowing that developers already “quickly” test their work with it?