Manning's Serious Web Development eBook Bundle on @humblebundle.com ends in 18 hours.
www.humblebundle.com/books/seriou...
#books #ref #deals #react #javascript #ai #apis #rustlang #unittesting #typescript
Humble Tech Book Bundle: Serio...
Today I got reminded of a great video of GeePaw Hill about the “Five Underplayed Premises Of TDD”.
1. The money premise
2. The judgement premise
3. The chain premise
4. The correlation premise
5. The driving premise
https://principal-it.eu/2025/08/five-underplayed-premises-of-tdd/
https://dev.to/ashutoshsarangi/react-unit-testing-using-vitest-3926 - #Vitest with #React is a great #UnitTesting system. Nice getting started walk-through https://www.linkedin.com/in/ashutosh-sarangi-4a220a138/.
Unit tests are safety nets. They catch regressions before users do, document expected behavior, and give you confidence to refactor & ship faster. Every test today saves hours of bug-hunting tomorrow. #PHP #UnitTesting #DevOps
via @dotnet : 5 Copilot Chat Prompts .NET Devs Should Steal Today
https://ift.tt/GMD8cvr
#DotNet #GitHubCopilot #AI #SoftwareDevelopment #CodingTips #DevTools #UnitTesting #AsyncProgramming #Security #MockData #Programming #CSharp #DeveloperCommunity #TechInnova…
Правильный старт: как заложить фундамент проекта
Почему зрелый проект начинается не с кода, а с инфраструктуры? Рассказываю, как простая автоматизация, тесты и документация экономят время, нервы и спасают от хаоса, особенно если вы пишете код с помощью ИИ.
Boas práticas de programação fazem bem para as pesquisas quantitativas... e, por acaso, para a prática clínica:
https://blog.leonardof.med.br/2025/ckd-epi-sbn.html
Fui usar "teste de unidade" ("unit testing", em inglês) no código de análise estatística que eu estava escrevendo, e descobri que uma calculadora online da Sociedade Brasileira de Nefrologia estava errada.
I've just released #cmocka version 1.1.8:
* Set CMOCKA_LIBRARIES in package config for backwards compatibility
* Improve c_strreplace implementation
* Sanitize XML strings
* Update check for uintptr_t
* Require cmake >= 3.10
My next article on #Rust #UnitTesting is out:
https://jorgeortiz.dev/posts/rust_unit_testing_simplify_tests/
In this one I share some tips on simplifying the tests code.
Spread the word 
Over the years, I have taught several courses on 
automated testing (#UnitTesting), some of them focused on #Rust. I wanted to write a book 
with the materials I had created, but I have gone with the second best: publishing them in my blog. First one is out:
https://jorgeortiz.dev/posts/rust_unit_testing_test_types/
All of them are meant for hands-on learning 
. I hope you like them.
Comments are welcome and spreading the word is appreciated.
Automated tests in my survival mode quest plugin :D
Now I just have to write more of em 
https://github.com/sammypanda/MCJE-PlayerQuests-Plugin/pull/169
@encthenet Oh darn, yeah that's mildly annoying of numpy. But there's still the regular temporary file handling. Who knows, working with in-memory fake files may not even make a significant difference if you could do it, compared to temporary files if they live on, say, a shared memory partition. 
That won't work. It says so in the docs:
> pyfakefs will not work with Python libraries that use C libraries to access the file system.
Which is what numpy is doing.
@encthenet @rachelplusplus Dunno if you've considered this, or would consider it, but pytest has a plugin, pytest-fakefs (https://github.com/pytest-dev/pyfakefs), that implements an in-memory filesystem complete with file objects that you can use to test file handling code without having to put things on disk. IMO the plugin ecosystem for handling things like this is one of pytest's biggest advantages over unittest.
Or if you prefer, pytest also has built-in functionality that makes working with temporary files pretty easy.
A couple weeks ago, I gave a talk at @omt_conf on What's New in Testing. That talk was recorded, but while I wait for it to be edited and published, I published an edited (and updated!) version of my speaker notes from that talk.
There's a lot new in testing since last year. I'm still surprised there wasn't a WWDC video about all the new things you can do.
https://rachelbrindle.com/2025/06/26/whats-new-in-testing-swift-6-2/
Простые вещи, которых я не знаю: юнит-тесты
В этом топике я не пытаюсь доказать, что тесты бесполезны. Это скорее мои размышления вслух и личная попытка нащупать их реальную ценность. Некоторые идеи в процессе всё-таки зацепили - но скорее как частные случаи, а не что-то универсальное. Я программирую уже больше шести лет. На самом деле существенно больше (на свой первый аутсорс на PHP я попал примерно в 2016 году), но осознанно подходить к своей карьере я начал не сразу. За это время я вполне успешно поработал в довольно разных местах, от маленьких стартапов до международных компаний. Недавно я проходил очередное собеседование, и на мой взгляд я неплохо держался. Как минимум до вопроса о том, как я покрываю свой код тестами. После него я стыдливо пробормотал о том, что знаю, как работает assert в python, и даже слышал про pytest. И что я с радостью начну писать тесты как только попаду к ним на проект, просто в наших проектах их не требовали. После чего мы плавно перешли к следующей теме, а оффер я так и не получил. Пришлось разбираться, что я делаю не так
I made a small tool called SpecSCAD to help write unit tests for #OpenSCAD functions using a #BDD-style syntax (describe, it, expect), inspired by Mocha/Jest. #UnitTesting
It runs @OpenSCAD in headless mode via Bash and outputs simple pass/fail results. No external dependencies beyond OpenSCAD + Bash.
It’s very lightweight, but can help to catch issues early in function-heavy code. Maybe it’s useful to others too — feedback welcome!
@nedbat I'm used to JUnit's assertEquals(expected, butgot) and it prints
Expected <<<x>>> but got <<<b>>>
Which is slightly better when you have long chunks of output (HTML and XML), butgot will be at the end instead of buried a page or two up. For short answers it doesn't matter.
#unitTesting #extremeProgramming #soExtreme!
Настраиваем CI/CD Android-проекта, часть 1. Начало
Всем привет, меня зовут Кирилл и я Android-разработчик в Scanny. Это первая часть из серии статей про CI/CD для Android-проекта. В рамках данной серии статей я расскажу как настраивать GitLab CI/CD, который покроет базовые потребности в Unit и Android-тестировании, сборке приложения, публикации в Play Market и многом другом. Дополнительно я разберу работу с разными инструментами для Android-тестирования в лице Marathon Labs и Firebase Test Lab. Аналогично разберу работу с Gradle Play Publisher и Fastlane для публикации приложения в Play Market.
️ 
