CLion 2026.1 Is Here
#Clang #CLion #News #Releases #Acp #Bazel #Cmake #Dap #Git #Unittesting

https://blog.jetbrains.com/clion/2026/03/2026-1-release/

New article: Tales Of TDD - One Test Double To Rule Them All
A short story about the pragmatic use of test doubles.
https://principal-it.eu/2026/03/tdd-tales-one-test-double/

#tdd #testdrivendevelopment #unittests #unittesting #softwaredesign

SaturdayMP Show 87: Creating PostCast (Part 9 – Figuring Out Testing in Go)

https://youtu.be/ISXbVjTKN4c

In this episode Omar and myself figure out how to add tests in Go. We try the built-in Go testing framework but then settle on using Testify. Testify allows writing assertions like other testing frameworks we are used to. We also experiment with different ways to do mocking Go and try to figure out what the Go error object is.

*PostCast is just a place holder name and might change. The goofy PostCast placeholder image was generated by ChatGPT and will likely change.

Go Testing:
https://go.dev/doc/tutorial/add-a-test

Testify:
https://github.com/stretchr/testify

Omar:
https://www.ashour.ca/

SaturdayMP:
https://saturdaymp.com/

PostCast Playlist:
https://www.youtube.com/playlist?list=PLYPcrKbLqwuvKQ97klk3bzyUPI6j154WC

Have a question you want answered in a future video? A challenging or interesting problem you need you want to see solved? Constructive feedback? Then comment, DM me, or send an email to [email protected].

Found this video useful? Then help others find it by liking, subscribing, sharing, and/or sponsoring:
https://github.com/sponsors/saturdaymp

Thanks for watching!

#saturdaymp #saturdaympshow #postcast #unittesting #mocking #golang

Interop between XCTest and Swift Testing? In the economy? It's more likely than you think.

Legitimately, I'm really excited for this. This'll enable much more consistent set of tooling that can easily be used in Swift Testing and in XCTest. It'll also make migrating from XCTest to Swift Testing much more simpler and much safer.

Go leave feedback at https://forums.swift.org/t/st-0021-targeted-interoperability-between-swift-testing-and-xctest/84965

#SwiftLang #XCTest #SwiftTesting #UnitTesting

Как писать юнит-тесты, которые не ломаются

Привет, Хабр! Меня зовут Владимир, я Python-разработчик в команде IMV в Авито . Мы разрабатываем продукт, который помогает оценивать рыночную стоимость товара, будь то автомобиль, квартира или холодильник. Мы часто пишем тесты, и в этой статье я расскажу, как разные подходы к юнит-тестированию влияют на качество тестов, когда они помогают проекту, а когда — мешают, и почему само по себе наличие тестов ещё не гарантирует пользы. Статья будет полезна разработчикам, тимлидам и всем, кто пишет юнит-тесты и поддерживает код в долгоживущих проектах.

https://habr.com/ru/companies/avito/articles/1001170/

#тестирование #unittesting #avito #avitotech #авито #testing #python #pytest #вебразработка

Надежный код: как писать тесты, чтобы запускать фичи в продакшен одним днем

Писать или не писать тесты — выбор очевидный. Конечно, писать. Но если проект масштабный, одних unit‑тестов будет недостаточно: они бессильны на границах модулей, в интеграциях и пользовательских сценариях, а значит в этих местах будут пролезать баги. Такой код будет сложно поддерживать, вносить в него изменения и получать ожидаемый результат. В статье поговорим про разные стратегии тестирования под разные риски и кейсы. Поднимемся над привычными unit‑тестами и заглянем, что там есть еще. Спойлер: а еще там workflow‑, integration‑, property‑based‑ и resilience‑тесты.

https://habr.com/ru/companies/mindbox/articles/1000090/

#C# #unittesting #integration_testing #propertybasedtesting #pure_functions #clean_architecture

via @dotnet : GitHub Copilot Testing for .NET Brings AI-powered Unit Tests to Visual Studio 2026

https://ift.tt/OunQHED
#GitHubCopilot #CopilotTesting #DotNet #CSharp #VisualStudio #VS2026 #GeneralAvailability #UnitTesting #AITesting #TestingWorkflow #TestGenera…

I like #UnitTesting. The original #SUnit was wonderful, but it was ported to the land of needless complexity and became #JUnit which begat a whole lot of add on pieces. A simple idea buried under feature creep.

My favorite testing framework is #SRFI-78 https://srfi.schemers.org/srfi-78/srfi-78.html which provides a little reporting and summarization but it doesn't interfere with the tests. In C the MinUnit header file from Jera Design is beautiful. I use a beefier implementation, again to get simple reporting.

#Forth has ttester. It is terse to the point that I am tempted to add some reporting. So far I've resisted the temptation.

As in SRFI-78, you test a phrase and compare against expected results on the stack.

T{ 1 2 3 drop -> 1 2 }T passes
T{ 1 2 3 dup -> 1 2 3 }T fails

I'm writing tests for my library code and use them to test expressions in my AoC efforts.

I'm trying to decide if I should include the test in the library source (compiled conditionally) or in separate test-* files. #Programming

A test suite is to its software
as a map is to its territory.
_________
("The map is not the territory.")

—Vassil, arms covered in virtual grease to the elbows,
having fun fixing a test suite (whose software seems to work).

--␠
My other signature is really witty.

#ComputerProgramming
#SoftwareEngineering
#TestingSoftware
#UnitTesting
#UnitTests