Veganism Social

David GardinerBlogged: Snapshot testing in .NET with Verify<a href="http://david.gardiner.net.au/2025/07/verify" rel="nofollow noopener" translate="no" target="_blank">http://david.gardiner.net.au/2025/07/verify</a><a href="https://mastodon.online/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnet</a> <a href="https://mastodon.online/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://mastodon.online/tags/SnapshotTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SnapshotTesting</a>

Leonardo Ferreira FontenelleBoas práticas de programação fazem bem para as pesquisas quantitativas... e, por acaso, para a prática clínica:<a href="https://blog.leonardof.med.br/2025/ckd-epi-sbn.html" rel="nofollow noopener" translate="no" target="_blank">https://blog.leonardof.med.br/2025/ckd-epi-sbn.html</a>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.<a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://mastodon.social/tags/RStats" class="mention hashtag" rel="nofollow noopener" target="_blank">#RStats</a> <a href="https://mastodon.social/tags/Medicina" class="mention hashtag" rel="nofollow noopener" target="_blank">#Medicina</a>

Andreas SchneiderI've just released <a href="https://mastodon.social/tags/cmocka" class="mention hashtag" rel="nofollow noopener" target="_blank">#cmocka</a> 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<a href="https://cmocka.org/" rel="nofollow noopener" translate="no" target="_blank">https://cmocka.org/</a><a href="https://mastodon.social/tags/unittesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittesting</a>

Jorge D. Ortiz-FuentesMy next article on <a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> <a href="https://fosstodon.org/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> is out: <a href="https://jorgeortiz.dev/posts/rust_unit_testing_simplify_tests/" rel="nofollow noopener" translate="no" target="_blank">https://jorgeortiz.dev/posts/rust_unit_testing_simplify_tests/</a> In this one I share some tips on simplifying the tests code. Spread the word 😉

Victor Nava<a href="https://bijaiv.com/tags/TestingPyramid" class="mention hashtag" rel="nofollow noopener" target="_blank">#TestingPyramid</a> <a href="https://bijaiv.com/tags/SoftwareTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareTesting</a> <a href="https://bijaiv.com/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://bijaiv.com/tags/IntegrationTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#IntegrationTesting</a> <a href="https://bijaiv.com/tags/E2ETesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#E2ETesting</a> <a href="https://bijaiv.com/tags/TestAutomation" class="mention hashtag" rel="nofollow noopener" target="_blank">#TestAutomation</a> <a href="https://bijaiv.com/tags/DevTips" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevTips</a> <a href="https://bijaiv.com/tags/QualityAssurance" class="mention hashtag" rel="nofollow noopener" target="_blank">#QualityAssurance</a> <a href="https://bijaiv.com/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareEngineering</a><a href="https://victornava.dev/2025/07/08/the-testing-pyramid-what-to-test-where-and-why-it-matters/" rel="nofollow noopener" translate="no" target="_blank">https://victornava.dev/2025/07/08/the-testing-pyramid-what-to-test-where-and-why-it-matters/</a>

sammypandaAutomated tests in my survival mode quest plugin :DNow I just have to write more of em :polarbear: <a href="https://github.com/sammypanda/MCJE-PlayerQuests-Plugin/pull/169" rel="nofollow noopener" translate="no" target="_blank">https://github.com/sammypanda/MCJE-PlayerQuests-Plugin/pull/169</a><a href="https://mastodon.social/tags/Minecraft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Minecraft</a> <a href="https://mastodon.social/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#Java</a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://mastodon.social/tags/MinecraftPlugin" class="mention hashtag" rel="nofollow noopener" target="_blank">#MinecraftPlugin</a>

David Zaslavsky<a href="https://flyovercountry.social/@encthenet" class="u-url mention" rel="nofollow noopener" target="_blank">@encthenet</a> 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. 🤷<a href="https://techhub.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

John-Mark Gurney<a href="https://techhub.social/@diazona" class="u-url mention" rel="nofollow noopener" target="_blank">@diazona</a><a href="https://tech.lgbt/@rachelplusplus" class="u-url mention" rel="nofollow noopener" target="_blank">@rachelplusplus</a>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. <a href="https://flyovercountry.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://flyovercountry.social/tags/pytest" class="mention hashtag" rel="nofollow noopener" target="_blank">#pytest</a> <a href="https://flyovercountry.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

David Zaslavsky<a href="https://flyovercountry.social/@encthenet" class="u-url mention" rel="nofollow noopener" target="_blank">@encthenet</a> <a href="https://tech.lgbt/@rachelplusplus" class="u-url mention" rel="nofollow noopener" target="_blank">@rachelplusplus</a> Dunno if you've considered this, or would consider it, but pytest has a plugin, pytest-fakefs (<a href="https://github.com/pytest-dev/pyfakefs" rel="nofollow noopener" translate="no" target="_blank">https://github.com/pytest-dev/pyfakefs</a>), 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 href="https://techhub.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://techhub.social/tags/pytest" class="mention hashtag" rel="nofollow noopener" target="_blank">#pytest</a> <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

Rachel BrindleA couple weeks ago, I gave a talk at <a href="https://mastodon.social/@omt_conf" class="u-url mention" rel="nofollow noopener" target="_blank">@omt_conf</a> 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.<a href="https://rachelbrindle.com/2025/06/26/whats-new-in-testing-swift-6-2/" rel="nofollow noopener" translate="no" target="_blank">https://rachelbrindle.com/2025/06/26/whats-new-in-testing-swift-6-2/</a><a href="https://hachyderm.io/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/WWDC2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#WWDC2025</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

Paul A. Jones, Jr.In fast-paced SaaS dev, unit tests aren't just insurance— they're leverage. Run them constantly. Automate the grind. Let tests catch regressions before your users do.” <a href="https://mastodon.social/tags/SaaSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#SaaSDev</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://mastodon.social/tags/BuildInPublic" class="mention hashtag" rel="nofollow noopener" target="_blank">#BuildInPublic</a>

Matthias Dittgen :bc:I made a small tool called SpecSCAD to help write unit tests for <a href="https://toot.community/tags/OpenSCAD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSCAD</a> functions using a <a href="https://toot.community/tags/BDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#BDD</a>-style syntax (describe, it, expect), inspired by Mocha/Jest. <a href="https://toot.community/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> It runs <a href="https://floss.social/@OpenSCAD" class="u-url mention" rel="nofollow noopener" target="_blank">@OpenSCAD</a> 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!

Rachel BrindleMy talk at OneMoreThing 2024 on <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://hachyderm.io/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftUI</a> and <a href="https://hachyderm.io/tags/SwiftConcurrency" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftConcurrency</a> was recorded, but has yet to be edited and uploaded. Last night, I published an edited form of my speaker notes from that talk to my blog.<a href="https://blog.rachelbrindle.com/2025/06/12/testing-swiftui-and-swiftconcurrency/" rel="nofollow noopener" translate="no" target="_blank">https://blog.rachelbrindle.com/2025/06/12/testing-swiftui-and-swiftconcurrency/</a><a href="https://hachyderm.io/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftLang</a>

Darren J. McLeodFor a long time, when I first started writing tests, I felt so unproductive writing tests. I would try to write the test as fast as possible so I could move on to the "real" code.Then one day when a production deployment failed due to missing a simple test I realized the critical value of tests... <a href="https://www.darrenmcleod.com/2025/06/test-code.html" rel="nofollow noopener" translate="no" target="_blank">https://www.darrenmcleod.com/2025/06/test-code.html</a> <a href="https://techhub.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareDevelopment</a> <a href="https://techhub.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a> <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

Fake Scrum Stats Memes & Humor<a href="https://techhub.social/tags/scrum" class="mention hashtag" rel="nofollow noopener" target="_blank">#scrum</a> <a href="https://techhub.social/tags/scrumteam" class="mention hashtag" rel="nofollow noopener" target="_blank">#scrumteam</a> <a href="https://techhub.social/tags/dev" class="mention hashtag" rel="nofollow noopener" target="_blank">#dev</a> <a href="https://techhub.social/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer</a> <a href="https://techhub.social/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://techhub.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://techhub.social/tags/unittests" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittests</a> <a href="https://techhub.social/tags/unittest" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittest</a> <a href="https://techhub.social/tags/unittestcoverage" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittestcoverage</a> <a href="https://techhub.social/tags/unittestingmuch" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittestingmuch</a> <a href="https://techhub.social/tags/Meme" class="mention hashtag" rel="nofollow noopener" target="_blank">#Meme</a> <a href="https://techhub.social/tags/memes" class="mention hashtag" rel="nofollow noopener" target="_blank">#memes</a> <a href="https://techhub.social/tags/Humor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Humor</a> <a href="https://techhub.social/tags/humour" class="mention hashtag" rel="nofollow noopener" target="_blank">#humour</a>

Rachel BrindleSometimes you gotta sherlock yourself. I think that Swift Testing should have something akin to Nimble's Polling Expectations.<a href="https://forums.swift.org/t/pitch-polling-expectations/79866" rel="nofollow noopener" translate="no" target="_blank">https://forums.swift.org/t/pitch-polling-expectations/79866</a>Also, wow, macros are hard. I am so glad I don't have to write them on a day-to-day basis.<a href="https://hachyderm.io/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

Ramin Honary<a href="https://www.well-typed.com/blog/2023/04/falsify/%20" rel="nofollow noopener" target="_blank">Property-based testing in Haskell with QuickCheck <code>falsify</code></a> A few days ago, Edsko de Vries of Well-Typed published an in-depth article on property-based software testing, with a focus on the concept of “shrinking.”In brief, property-based testing is sort-of like fuzz testing but for algorithms and protocols. Like fuzz testing, random test cases are procedurally generated, but unlike fuzz testing, the test cases are carefully designed to verify whether a software implementation of an algorithm satisfies a specific property of that algorithm, such as:<ul><li>“this function always fails if the index is larger than the array”</li><li>“this function always returns a result in <code>n*log(n)</code> number of iterations for input dataset of size <code>n</code>“</li><li>“the sequence of log messages is guaranteed to obey this rules of this particular finite-state automata: (connect | fail) -> (send X | fail) -> (receive Y | receive Z | fail) -> success .”</li></ul>Shrinking is the process of simplifying a failed test case. If you have found some input that makes your function return a value when it should have thrown an exception, or produce a result that does not satisfy some predicate, then that input is a “counterexample” to your assertion about the properties of that function. And you may want to be able to “shrink” that counterexample input to see if you can cause the function to behave incorrectly again but with a simpler input. The “<a href="https://hackage.haskell.org/package/QuickCheck%20" rel="nofollow noopener" target="_blank">QuickCheck</a>“ library provides a variety of useful tools to let you define property tests with shrinking.Defining unit tests with such incredible rigor takes quite a lot of time and effort, so you would probably do not want to use property-based testing for your ordinary, every-day software engineering. If you are, for example, being scrutinized by the US Department of Government of Efficiency, you would likely be fired if you were to take so much time to write such high-quality software with such a strong guarantee of correctness.But if you are, for example, designing a communication protocol that will be used in critical infrastructure for the next 10 or 20 years and you want to make sure the reference implementation of your protocol is without contradictions, or if you are implementing an algorithm where the mathematical properties of the algorithm fall within some proven parameters (e.g. computational complexity), property-based testing can give you a much higher degree of confidence in the correctness of your algorithm or protocol specification.<a class="hashtag" href="https://fe.disroot.org/tag/tech" rel="nofollow noopener" target="_blank">#tech</a> <a class="hashtag" href="https://fe.disroot.org/tag/software" rel="nofollow noopener" target="_blank">#software</a> <a class="hashtag" href="https://fe.disroot.org/tag/haskell" rel="nofollow noopener" target="_blank">#haskell</a> <a class="hashtag" href="https://fe.disroot.org/tag/welltyped" rel="nofollow noopener" target="_blank">#WellTyped</a> <a class="hashtag" href="https://fe.disroot.org/tag/quickcheck" rel="nofollow noopener" target="_blank">#QuickCheck</a> <a class="hashtag" href="https://fe.disroot.org/tag/unittesting" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a class="hashtag" href="https://fe.disroot.org/tag/propertytesting" rel="nofollow noopener" target="_blank">#PropertyTesting</a>

Khalid K-1000 🤖🚀 Neat! <a href="https://mastodon.social/tags/Duende" class="mention hashtag" rel="nofollow noopener" target="_blank">#Duende</a> is sponsoring <a href="https://mastodon.social/tags/dotnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#dotnet</a> project Shouldy for the next year for $3,000. <a href="https://mastodon.social/tags/unittesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittesting</a> <a href="https://mastodon.social/tags/xunit" class="mention hashtag" rel="nofollow noopener" target="_blank">#xunit</a> <a href="https://mastodon.social/tags/nunit" class="mention hashtag" rel="nofollow noopener" target="_blank">#nunit</a> <a href="https://mastodon.social/tags/mstest" class="mention hashtag" rel="nofollow noopener" target="_blank">#mstest</a><a href="https://blog.duendesoftware.com/posts/20250415-shouldly-assertion-framework/" rel="nofollow noopener" translate="no" target="_blank">https://blog.duendesoftware.com/posts/20250415-shouldly-assertion-framework/</a>

Rachel BrindleThe testing attachments proposal has been accepted (with modifications)! To be attached to some upcoming swift version! <a href="https://forums.swift.org/t/accepted-with-modifications-st-0009-attachments/79193" rel="nofollow noopener" translate="no" target="_blank">https://forums.swift.org/t/accepted-with-modifications-st-0009-attachments/79193</a>No real negative feedback, either. I guess people quickly became attached to the idea.There were some disagreements about naming in the review, but I’m glad that we resolved that amicably. I’d really hate it if we were too attached to an idea to come to an agreement.<a href="https://hachyderm.io/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> <a href="https://hachyderm.io/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

Rachel BrindleAdding Attachments to Swift Testing is up for review! It's my first time being a review manager.Forum thread: <a href="https://forums.swift.org/t/st-0009-attachments/78698" rel="nofollow noopener" translate="no" target="_blank">https://forums.swift.org/t/st-0009-attachments/78698</a>Proposal: <a href="https://github.com/swiftlang/swift-evolution/blob/main/proposals/testing/0009-attachments.md" rel="nofollow noopener" translate="no" target="_blank">https://github.com/swiftlang/swift-evolution/blob/main/proposals/testing/0009-attachments.md</a><a href="https://hachyderm.io/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> <a href="https://hachyderm.io/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>

Recent searches

Search options

Administered by:

Server stats:

#unittesting