# code testing

Published articles for code testing.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Behind the Flame: Joe Hart

DevFeed: [Behind the Flame: Joe Hart](<https://devfeed.tech/articles/behind-the-flame-joe-hart-11650.md>)

Original publisher: [Read original article](<https://incident.io/blog/behind-the-flame-joe-hart>)

Author: Megan Batterbury

Published: 2026-04-23T10:00:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [incident management](<https://devfeed.tech/topics/incident-management.md>), [dashboards](<https://devfeed.tech/topics/dashboards.md>), [Code](<https://devfeed.tech/topics/code.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [code-testing](<https://devfeed.tech/tags/code-testing.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [developer](<https://devfeed.tech/tags/developer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [slack](<https://devfeed.tech/tags/slack.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>), [testing](<https://devfeed.tech/tags/testing.md>), [tools](<https://devfeed.tech/tags/tools.md>), [work](<https://devfeed.tech/tags/work.md>), [writing-code](<https://devfeed.tech/tags/writing-code.md>)

### AI overview

This profile introduces Joe Hart, a Product Engineer on incident.io's Response team. It describes his work on status pages, the incident management lifecycle, integrations, dashboards, customer issues, coding, testing, and collaboration across engineering teams.

### Source excerpt

Meet Joe Hart, Product Engineer here at incident.io. 🔥

## 6 Testing Mistakes You Should Avoid

DevFeed: [6 Testing Mistakes You Should Avoid](<https://devfeed.tech/articles/6-testing-mistakes-you-should-avoid-26198.md>)

Original publisher: [Read original article](<https://craftbettersoftware.com/p/6-testing-mistakes-you-should-avoid>)

Author: Daniel Moka

Published: 2025-04-05T05:00:42Z

Content type: tutorial

Language: en

Sources: [Craft Better Software](<https://devfeed.tech/sources/craft-better-software.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [mutation-testing](<https://devfeed.tech/topics/mutation-testing.md>), [Development](<https://devfeed.tech/topics/development.md>), [clean-code](<https://devfeed.tech/topics/clean-code.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [clean-code](<https://devfeed.tech/tags/clean-code.md>), [code-testing](<https://devfeed.tech/tags/code-testing.md>), [mutation-testing](<https://devfeed.tech/tags/mutation-testing.md>), [shift-left](<https://devfeed.tech/tags/shift-left.md>), [solid-principles](<https://devfeed.tech/tags/solid-principles.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

A practical guide to avoiding common testing mistakes, including testing late, relying too heavily on code coverage, testing implementation details, and neglecting clean test code. It recommends shift-left testing, mutation testing, behavior-focused tests through public APIs, and treating tests as maintainable code.

### Source excerpt

Each with a simple fix you can apply today

## What the fuzz? Better coding through randomized testing

DevFeed: [What the fuzz? Better coding through randomized testing](<https://devfeed.tech/articles/what-the-fuzz-better-coding-through-randomized-testing-13320.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/what-the-fuzz-better-coding-through-randomized-testing>)

Published: 2023-03-13T00:00:00Z

Content type: opinion

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [code-testing](<https://devfeed.tech/tags/code-testing.md>), [debug](<https://devfeed.tech/tags/debug.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [python](<https://devfeed.tech/tags/python.md>), [research](<https://devfeed.tech/tags/research.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-testing](<https://devfeed.tech/tags/software-testing.md>), [techniques](<https://devfeed.tech/tags/techniques.md>), [test](<https://devfeed.tech/tags/test.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

This Chainguard article explains how randomized testing and fuzzing can help developers find complicated software bugs. It presents randomized testing as complementary to test-driven development and discusses choosing testing techniques for the right applications.

### Source excerpt

Why do we test our code? Find out in this Chainguard post on the benefits of randomized testing and fuzzing practices.

## How to test intermediate steps in suspending functions

DevFeed: [How to test intermediate steps in suspending functions](<https://devfeed.tech/articles/how-to-test-intermediate-steps-in-suspending-functions-37170.md>)

Original publisher: [Read original article](<https://arkadiuszchmura.com/posts/how-to-test-intermediate-steps-in-suspending-functions/>)

Published: 2022-09-30T00:00:00Z

Content type: tutorial

Language: en

Sources: [Arkadiusz Chmura](<https://devfeed.tech/sources/arkadiusz-chmura.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [Coroutines](<https://devfeed.tech/topics/coroutines.md>), [execution](<https://devfeed.tech/topics/execution.md>)

Tags: [code-testing](<https://devfeed.tech/tags/code-testing.md>), [coroutines](<https://devfeed.tech/tags/coroutines.md>), [dispatcher](<https://devfeed.tech/tags/dispatcher.md>), [scheduler](<https://devfeed.tech/tags/scheduler.md>), [testing](<https://devfeed.tech/tags/testing.md>), [virtual](<https://devfeed.tech/tags/virtual.md>)

### AI overview

This tutorial explains how to test intermediate state changes inside suspending functions. It shows how coroutine test dispatchers and virtual-time controls can verify behavior before and after a suspended network call without waiting through real delays.

### Source excerpt

Testing the final result of a suspending function is easy, but what about verifying what happens inside it during the execution?

## Integrating Development and Testing to Improve Software Quality at FINN.no

DevFeed: [Integrating Development and Testing to Improve Software Quality at FINN.no](<https://devfeed.tech/articles/qa-role-is-dead-but-development-and-testing-together-provides-quality-for-finn-no-31962.md>)

Original publisher: [Read original article](<https://tech.finn.no2012/05/07/qa-role-is-dead-but-development-and-testing-together-provides-quality-for-finn/>)

Author: vivek

Published: 2012-05-07T07:29:20Z

Content type: opinion

Language: en

Sources: [Finn.no](<https://devfeed.tech/sources/finn-no.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [Development](<https://devfeed.tech/topics/development.md>), [Cucumber](<https://devfeed.tech/topics/cucumber.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [code-testing](<https://devfeed.tech/tags/code-testing.md>), [development](<https://devfeed.tech/tags/development.md>), [qa](<https://devfeed.tech/tags/qa.md>), [quality-assurance](<https://devfeed.tech/tags/quality-assurance.md>), [regression](<https://devfeed.tech/tags/regression.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article argues that testing should be integrated into the development process rather than treated as a separate quality assurance department. At FINN, teams without a dedicated QA role reportedly achieved the same quality as teams with QA by sharing responsibilities and using different task-management practices.

### Source excerpt

When a developer is finished with a development issue, it must be tested. People often think the goal of testing should be to find all the errors. Well, it's not entirely realistic. Actually, it's impossible! Despite the title of "quality insurance" testers can never really ensure level of quality, nor can they be expected to find all the errors. The real goal of testing should be to improve the software. As at the end of the day we want to minimize the cost of fixing critical bugs after a release, minimize cost of handling customer complaints and pushing a patch in the production. So it is import to understand that Quality Assurance is a process, not a department. Today there are basically two different components of QA role in FINN. One of which is "QA in a team" and the other one is of a "team without the QA". The QA role today is often a safety net for many developers and teams. The role involves manual testing in the sprint, regression testing and writing Cucumber tests. In addition this role has some administrative tasks such as being contact person for the Release Manager, participating in the release status meeting, filling out the checklist of early / late shift, contact for Tech Support (E-journal issues), participating in status meetings at Call Center after release, and verifying the patch to production. Everything that's listed so far is managed also by teams without QA. What we have seen so far, is that a team without QA delivers the same quality as the team with QA in developing an FINN application. Then comes the question, how do they manage to do it? They have the same responsibilities as the "QA in a team", but they have different practices on how they manage the tasks (some have rolling QA role, others have a fixed arrangement but they are NOT dependent on one individual person). If we want to deliver a good quality code, testing must become a central pillar of the development process. When I say the role of QA is dead, but development and testing