Daniel EversLately, I worked on a bunch of development tools and made them "nicer" using bash completion. But I have never seen any unit tests for completion functions...
Since I'm a test-driven developer, I'm wondering if anybody ever tried this?!
Jon ReidThe Trade-Offs of ViewInspector (And Why They're Worth It) https://qualitycoding.org/viewinspector-risks-benefits/ #UnitTesting
CLion Blog
Jan Van RyswyckNew 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
Chris CSaturdayMP Show 87: Creating PostCast (Part 9 – Figuring Out Testing in Go)
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
SaturdayMP Show 87: Creating PostCast (Part 9 – Figuring Out Testing in Go)
Rachel BrindleInterop 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
ST-0021: Targeted Interoperability between Swift Testing and XCTest
Hello Swift Community! The review of ST-0021 "Targeted Interoperability between Swift Testing and XCTest" starts now and runs through Tuesday, March 10th, 2026. The proposal is available here: swift-evolution/proposals/testing/0021-targeted-interoperability-swift-testing-and-xctest.md at main · swiftlang/swift-evolution · GitHub Reviews are an important part of the Swift evolution process. All review feedback should be either on this forum thread or, if you would like to keep your feedback pri...
HabrКак писать юнит-тесты, которые не ломаются
Привет, Хабр! Меня зовут Владимир, я 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
Brandon H 
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…
Peter Sommerlad@Sdowney GoogleTest is one of the worst legacy C++ design. I hate it and won't use it. however, the brand makes it too attractive for the uninitiated.
I also hate some of its features that allow you to write large tests (EXPECT instead of REQUIRE), where in my unit testing philosophy a test function should have a single reason to fail and be named like that.