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
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/
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.” #SaaSDev #UnitTesting #BuildInPublic
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!
My talk at OneMoreThing 2024 on #UnitTesting #SwiftUI and #SwiftConcurrency 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.
https://blog.rachelbrindle.com/2025/06/12/testing-swiftui-and-swiftconcurrency/
For 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... https://www.darrenmcleod.com/2025/06/test-code.html
Video 3 is out. You don't want the app launching (and mucking with networking, persistence, and analytics) during tests, do you? #Xcode #UnitTesting #SwiftUI https://www.youtube.com/watch?v=SSM2_a0_yIk
David Handlos presents 'Performance Testing In Practice' July 25th at Nebraska.Code().
Why Property Testing Finds Bugs Unit Testing Does Not (2021)
https://buttondown.com/hillelwayne/archive/why-property-testing-finds-bugs-unit-testing-does/
Cory House presents 'Effective Automated Testing - Lessons from 10 Years' July 24th at Nebraska.Code().
Sometimes you gotta sherlock yourself. I think that Swift Testing should have something akin to Nimble's Polling Expectations.
https://forums.swift.org/t/pitch-polling-expectations/79866
Also, wow, macros are hard. I am so glad I don't have to write them on a day-to-day basis.
Day 4 (the missing day): Building Data Import/Export Services for Your ERP System