> ## Content Index > Fetch the complete content index at: https://softwaretestingweekly.com/llms.txt > Use this file to discover other available public pages before exploring further. # Issue #3 - URL: https://softwaretestingweekly.com/issues/3/ - Published: 2020-01-24T16:28:20.000Z - Updated: 2026-06-10T13:17:01.000Z - Author: Dawid Dylowicz | Comment | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Welcome everyone! 🙌It's Friday again (time flies, right?) and I'm back with the third issue of Software Testing Weekly!The great thing about preparing this newsletter is that I discover really amazing resources during my research.I was surprised to find [Manning](https://www.manning.com/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) publications this week (about time, I know). I'm even more surprised by the [free book samples](https://freecontent.manning.com/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) that they share. But finding the whole book about unit testing published there for free?! It blew my mind! It's called *Unit Testing Principles, Practices and Patterns* by [Vladimir Khorikov](https://twitter.com/vkhorikov?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) and you can read it [here](https://livebook.manning.com/book/unit-testing/about-this-book/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3).Another wonderful thing I've found is this excellent wrap-up of [UI testing best practices](https://github.com/NoriSte/ui-testing-best-practices?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) by [Stefano Magni](https://twitter.com/NoriSte?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3). It's all nicely laid out, and it's open-source - meaning you can contribute to it too. I love it!Last but not least, a friendly reminder that you can [submit a link](https://morethantesting.typeform.com/to/JwoP5a?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) for the next issue. You can also follow this page on [Twitter](https://twitter.com/QANewsletter?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3).Enjoy the read!*[Dawid Dylowicz](https://twitter.com/ddylowicz?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)* | | | | NEWS | | [Testing and feedback loops](https://blog.nelhage.com/post/testing-and-feedback-loops/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)*"When I’m writing a program for the first time, I almost never worry about test coverage early on; instead I worry about setting up infrastructure that lets me cheaply capture any bugs I do find as test cases, and rely on later testing to increase coverage."*Really interesting article from [Nelson Elhage](https://twitter.com/nelhage?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) who presents a software engineer's point of view on improving coverage over time by using feedback loops from testing. I like the idea.[blog.nelhage.com](https://blog.nelhage.com/post/testing-and-feedback-loops/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [Risk Coverage: A New Currency for Testing](https://www.stickyminds.com/article/risk-coverage-new-currency-testing?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)*"If you want fast, accurate assessments of the risks associated with promoting the latest release candidate to production, you need a new currency in testing: Risk coverage needs to replace test coverage."*I've studied computer science, so maths always gets me. Here [Wolfgang Platz](https://twitter.com/WolfgangPlatz?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) proves in a mathematical way why the risk-based testing method can give much more insights than simple test coverage. Nice equations and graphs, by the way![stickyminds.com](https://www.stickyminds.com/article/risk-coverage-new-currency-testing?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [I don’t think that means what you think it means (Enterprise Software Testing Metrics)](http://qualityremarks.com/i-dont-think-that-means-what-you-think-it-means-enterprise-software-testing-metrics/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)I enjoyed this article by [Keith Klain](https://twitter.com/keithklain?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) where he shares his experience of working with metrics during one of his consulting projects, highlighting what's wrong with attempts to measure quality, and what's important about having valid metrics.[qualityremarks.com](http://qualityremarks.com/i-dont-think-that-means-what-you-think-it-means-enterprise-software-testing-metrics/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [First challenges as a new Product Owner](https://unremarkabletester.com/2020/01/21/first-challenges-as-a-new-product-owner/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)Software testing is evolving, and so are the roles. Some go towards programming, some choose product. Most recently, [Areti Panou](https://twitter.com/unremarkableQA?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) has become a Product Owner and she shares her first impressions about the role and how it is coming from software testing background.[unremarkabletester.com](https://unremarkabletester.com/2020/01/21/first-challenges-as-a-new-product-owner/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [New Managers: Creating culture](https://angelariggs.github.io/articles/new-managers-culture?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)The second article from the management series by [Angela Riggs](https://twitter.com/AngelaRiggs%5F?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) — an aftermath of her [tweet](https://twitter.com/AngelaRiggs%5F/status/1216078559346741249?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) that went viral. This time, she wraps up the advice she got about culture. This is to all of those who manage people, and those who are managed, too. Everyone, I mean, read it![angelariggs.github.io](https://angelariggs.github.io/articles/new-managers-culture?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | | | AUTOMATION | | [Web UI Automation (Protractor)](https://testifyqa.com/javascript-protractor-web-automation/part-1-getting-started-protractor/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)Tremendous effort by [Thomas Knee](https://twitter.com/QaTestify?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) who comprehensively explains web UI automation with [Protractor](https://www.protractortest.org/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3). The first part (linked above) is about getting started and setting up the tooling on macOS and Windows platforms.I highly recommend reading [part 2](https://testifyqa.com/javascript-protractor-web-automation/part-2-framework-structure-protractor/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) about framework structure and configuration, and [part 3](https://testifyqa.com/javascript-protractor-web-automation/part-3-creating-our-bdd-test/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) about creating BDD tests. Truly solid work![testifyqa.com](https://testifyqa.com/javascript-protractor-web-automation/part-1-getting-started-protractor/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [Fluent Builders in Automated Tests](https://medium.com/@blakenorrish/fluent-builders-in-automated-tests-5e031874958e?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)I haven't come across fluent builders before but this step-by-step article by [Blake Norrish](https://twitter.com/blakenorrish?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) made the concept perfectly clear to me. In essence, it's making the tests easy to read and write by hiding data when creating domain objects. Kudos![medium.com](https://medium.com/@blakenorrish/fluent-builders-in-automated-tests-5e031874958e?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [Practical test strategy for Spring & React application](https://www.awesome-testing.com/2020/01/practical-test-strategy-for-spring.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)I couldn't agree more with [Sławomir Radzymiński](https://twitter.com/s%5Fradzyminski?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) on the test strategy for any backend-frontend system. Great practical advice about tooling and lots of links to actual source code included.[awesome-testing.com](https://www.awesome-testing.com/2020/01/practical-test-strategy-for-spring.html?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [New Microsoft Edge and test automation](https://alexanderontesting.com/2020/01/21/faq-new-microsoft-edge-and-test-automation/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)If you missed the news, Microsoft has released [a brand new Edge browser](https://www.microsoft.com/en-us/edge?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) based on Chromium engine, making it available on all the popular operating systems. Edge on Mac?! Yup, it's happening! But what's up with testing it? Well, [Alexander Oliveira Dunn](https://twitter.com/AlexanderOnTest?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) got you covered by creating this really helpful FAQ-style post with answers you may want to see.[alexanderontesting.com](https://alexanderontesting.com/2020/01/21/faq-new-microsoft-edge-and-test-automation/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [9 Top Automation Testing Trends for 2020](https://testguild.com/trends-2020/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)Last but not least, [Joe Colantonio](https://twitter.com/joecolantonio?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) shared a nice compilation of automation areas that may get more attention this year. Some of the picks surprised me, in a positive way. I mean, AiOps?! How cool would that be![testguild.com](https://testguild.com/trends-2020/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | | | TOOLS | | [\[API\] HttpRider - a lightweight open-source REST API client](https://www.httprider.com/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3)[@deskriders\_twt](https://twitter.com/deskriders%5Ftwt/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) created a promising cross-platform REST API client that can be used as an alternative to [Postman](https://www.getpostman.com/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) for simpler tasks. And it's open-source![httprider.com](https://www.httprider.com/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) | | [\[Java\] JUnit 5.6.0 released](https://junit.org/junit5/docs/snapshot/release-notes/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3#release-notes-5.6.0)Some good news for those of you using [JUnit](https://twitter.com/junitteam?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3). After over 4 months of waiting, they've released a brand new 5.6.0 version.[junit.org](https://junit.org/junit5/docs/snapshot/release-notes/?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3#release-notes-5.6.0) | | | | And… | | [I wonder who introduced this bug...](https://imgur.com/5BN4A83?utm%5Fcampaign=Software%2BTesting%2BWeekly&utm%5Fsource=Software%5FTesting%5FWeekly%5F3) |