Tag software-testing

Do you think code coverage numbers are useless? Well, not if you use cover coverage reports to find missing test scenarios. @mauricioaniche explains how coverage reports can help you step up in your testing game. Full episode: software-engineering-unlocked.com/tests-find-bug…

Software Engineering Unlocked Podcast (@se_unlocked)Fri, 28 Jan 2022 16:43 GMT

This week I worked with a team to get code coverage over 80% (a corporate minimum). The problem with this effort: Code coverage can be gamed. Sure, low code coverage means there's a lot of untested code. But, high code coverage doesn't mean the code is well tested.

Cory House (@housecor)Sat, 30 Oct 2021 11:42 +0000

https://twitter.com/housecor/status/1454413465091821568

Low quality tests are arguably worse than no tests. Why? Because they make it look like the code is well tested. This creates a false sense of confidence. And lousy tests that report 100% coverage mask opportunities to improve. The real solution: Thoughtful, human review.

Cory House (@housecor)Sat, 30 Oct 2021 11:42 +0000

Unit testing requires significantly less skill, time investment, and infrastructure than any other form of testing and almost any other form of verification. So anybody can pick it up and apply it to any project. That's why it's the go-to technique

Post details

One thing I've wondered about is why software folks so often use unit testing as their go-to testing technique. When I've worked at companies that ship few enough bugs that it would be considered a failure to have one serious bug in a year, unit testing has been a last resort.

Dan Luu (@danluu)Tue, 11 May 2021 17:42 +0000

Hillel (@hillelogram)Tue, 11 May 2021 18:48 +0000

Mocking in unit tests makes the tests more stable because they don’t break when your code breaks.

Beth (@bethcodes)Tue, 29 Dec 2020 01:26 GMT

"how did QA miss this" - 99% of the time we didn't. qa don't decide what gets fixed, we just point at it

Post details

What phrase signals that the person using it doesn't understand your field? Example: "Computer error."

Paul Graham (@paulg)Wed, 26 Aug 2020 19:00 +0000

Jordan Garland 🤠 (@MostUnfurrowed)Fri, 28 Aug 2020 16:27 +0000

https://twitter.com/Maaikees/status/1275705458741911554

strong disagree. no unit or API test would catch these UI errors which impact a company's bottom line, and humans shouldn't be tasked with manually checking every page of your app over and over to catch these bugs.

Angie Jones (@techgirl1908)Wed, 24 Jun 2020 19:12 +0000