Social 📸 Photography

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

Brian Okken :python:Goodbye Michael Foord. You will be missed. - Nice write up by Nicholas Tollervey: <a href="https://ntoll.org/article/my-friend-michael/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://ntoll.org/article/my-friend-michael/</a> - 2021 interview with him: <a href="https://testandcode.com/episodes/145-for-those-about-to-mock-michael-foord" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://testandcode.com/episodes/145-for-those-about-to-mock-michael-foord</a><a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://fosstodon.org/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> <a href="https://fosstodon.org/tags/mock" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mock</a> <a href="https://fosstodon.org/tags/hoopyfrood" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hoopyfrood</a>

Jan :rust: :ferris:UwU, I've just found out about `SystemState` in <a href="https://floss.social/tags/Bevy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bevy</a> :awesome: <a href="https://docs.rs/bevy/latest/bevy/ecs/system/struct.SystemState.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://docs.rs/bevy/latest/bevy/ecs/system/struct.SystemState.html</a>It basically allows you to circumvent (mutable) borrowing issues with `App` and `World` when you have exclusive `World` access. As it turns out, this is especially useful in <a href="https://floss.social/tags/UnitTests" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTests</a>. 🧪 ✅ See next two toots for an example...1/3<a href="https://floss.social/tags/BevyEngine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BevyEngine</a> <a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://floss.social/tags/Testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Testing</a> <a href="https://floss.social/tags/GameDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GameDev</a> <a href="https://floss.social/tags/BevyUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BevyUI</a> <a href="https://floss.social/tags/UI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UI</a>

Hugo van KemenadeOh, and taking inspiration from <a href="https://mastodon.social/tags/pytest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pytest</a>, I added colour to <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> output in this one 🎨<a href="https://docs.python.org/3.14/whatsnew/3.14.html#unittest" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://docs.python.org/3.14/whatsnew/3.14.html#unittest</a> <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://mastodon.social/tags/CPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPython</a> <a href="https://mastodon.social/tags/Python314" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python314</a> <a href="https://mastodon.social/tags/release" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#release</a>

Jan :rust: :ferris:Code in <a href="https://floss.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> is so correct that the reason your <a href="https://floss.social/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> fails is solely because of wrong <a href="https://floss.social/tags/test" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#test</a> data.¯\_(ツ)_/¯Rust is as close to <a href="https://floss.social/tags/magic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#magic</a> as you can get as a <a href="https://floss.social/tags/SoftwareEngineer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineer</a>. ✨ <a href="https://floss.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a>

Denis 🌏hell is unit tests that pass locally and fail inexplicably on CI<a href="https://hachyderm.io/tags/amCoding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amCoding</a> <a href="https://hachyderm.io/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a> <a href="https://hachyderm.io/tags/unitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unitTest</a>

Jan :rust: :ferris:Wondering why your (unit) test fails?You might have changed the test data, but have you also considered changing the appropriate flags of your class under test when copying an existing test over!?(don't ask why I'm telling you this😳)<a href="https://floss.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://floss.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a> <a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://floss.social/tags/UnitTests" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTests</a>

Fink :antifa:Let's better not use <a href="https://chaos.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://chaos.social/tags/pytest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pytest</a> and instead continue with <a href="https://chaos.social/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a>. (OK so far) And do wired stuff in the code base we want to test because of that. (The fuck)How do you argue against testing with in some places more than 5 stacked "with mock x:"? Yes not even "with mock x, mock y, mock z:".Also people arguing with "i like it better" and ignoring actual arguments?

Jan :rust: :ferris:<a href="https://mastodon.online/@shuttle" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@shuttle</a> I consequently use <a href="https://floss.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>, where possible.Yes, sure, <a href="https://floss.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> prevents a lot of bugs at compile time already, but not logic bugs.For example in <a href="https://floss.social/tags/CSVDiff" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CSVDiff</a> we have ~70 unit tests and ~12 integration tests. The only "bug report" we have ever gotten was due to a corrupted CSV file (being mistaken with a bug in diff):See here (qsv): <a href="https://github.com/jqnatividad/qsv/issues/1258#issuecomment-1712924932" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/jqnatividad/qsv/issues/1258#issuecomment-1712924932</a>csv-diff: <a href="https://gitlab.com/janriemer/csv-diff" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.com/janriemer/csv-diff</a>In the future I'd like to add property and mutation testing as well 🤓 <a href="https://floss.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> <a href="https://floss.social/tags/Testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Testing</a> <a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a>

Jan :rust: :ferris:Writing some more unit tests in <a href="https://floss.social/tags/Bevy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bevy</a> <a href="https://floss.social/tags/BevyEngine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BevyEngine</a> for the dragndrop plugin (by cadyn - see below) right now. It is so much fun and I already discovered a small bug (the test is red ❌)! 🙂 🐛 Going to fix it now. 💪 Hopefully, I'm able to get it to green ✅ Let's see...<a href="https://github.com/cadyn/bevy_dragndrop" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/cadyn/bevy_dragndrop</a><a href="https://floss.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> <a href="https://floss.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> <a href="https://floss.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a> <a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a>

Daniel BöhmerTest Driven Development sometimes is a huge disappointment to me:I was writing the test first, and then got really surprised that the new method can’t be called because it’s kinda not implemented. How can that be?! 😠 Oh, I see … 🤡 <a href="https://chirp.social/@Perl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Perl</a> <a href="https://ieji.de/tags/testdrivendevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testdrivendevelopment</a> <a href="https://ieji.de/tags/tdd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tdd</a> <a href="https://ieji.de/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://ieji.de/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a>

Jan :rust: :ferris:And this is why <a href="https://floss.social/tags/UnitTests" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTests</a> and <a href="https://floss.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a> are awesome/necessary (even in <a href="https://floss.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a>/ <a href="https://floss.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a>):The original requirement: figure out how many columns the _result_ of diffing two CSVs in <a href="https://floss.social/tags/CsvDiff" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CsvDiff</a> have.Do you see the error-pattern?It's - when we have no diff && - at least one CSV has headerswhich makes sense, because I've implemented the feature in the diffing logic, but at that point header information is already lost (in some other thread).Isn't that beautiful!?🥰 <a href="https://floss.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a>

Digital Mark λ ☕️ 🕹 🙄<a href="https://oldbytes.space/@arclight" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@arclight</a> I don't usually write black box tests (pinging thru the app with mocks), that's QA. I just unit test by function, what it's supposed to do on happy path and some failure paths.Testing anything above one function means if you want to change any workflow your tests break for no good reason.I used to care about the XP "test first, see red bar, implement, see green bar" thing but I use less shitty languages than Java now, so it's less urgent. <a href="https://appdot.net/tags/tdd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tdd</a> <a href="https://appdot.net/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a>

Khalid Pro Max⚡️<a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://mastodon.social/tags/test" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#test</a> <a href="https://mastodon.social/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> <a href="https://mastodon.social/tags/dotnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dotnet</a> <a href="https://mastodon.social/tags/javascript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#javascript</a>

Jan :rust: :ferris:Unit-testing a web service in <a href="https://floss.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> - by Julio Merino<a href="https://jmmv.dev/2023/07/unit-testing-a-web-service.html" rel="nofollow noopener noreferrer" target="_blank">https://jmmv.dev/2023/07/unit-testing-a-web-service.html</a><a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://floss.social/tags/WebService" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebService</a> <a href="https://floss.social/tags/Testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Testing</a> <a href="https://floss.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://floss.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a>

AnguSince XCTest does not support async expressions in its assert functions I released SwiftAsyncAsserts Swift package to fill that gap.Write more readable testing code for your async type interfaces in Swift.<a href="https://github.com/angu-software/SwiftAsyncAssert" rel="nofollow noopener noreferrer" target="_blank">https://github.com/angu-software/SwiftAsyncAssert</a><a href="https://techhub.social/tags/swift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swift</a> <a href="https://techhub.social/tags/xctest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xctest</a> <a href="https://techhub.social/tags/asyncawait" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asyncawait</a> <a href="https://techhub.social/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> <a href="https://techhub.social/tags/swiftdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swiftdev</a> <a href="https://techhub.social/tags/iosdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iosdev</a> <a href="https://techhub.social/tags/macdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macdev</a>

Jan :rust: :ferris:Have you also verified what happens when you call your method twice?🤓 ✌️ <a href="https://floss.social/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Programming</a> <a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://floss.social/tags/Testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Testing</a> <a href="https://floss.social/tags/Quality" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Quality</a>

Jan :rust: :ferris:SoftwareDev.assert('no unit tests', INSANITY);Passed: 1 Failed: 0<a href="https://floss.social/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDevelopment</a> <a href="https://floss.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://floss.social/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> <a href="https://floss.social/tags/Testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Testing</a> <a href="https://floss.social/tags/Quality" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Quality</a> <a href="https://floss.social/tags/Insanity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Insanity</a> <a href="https://floss.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>

xUnit.netIt's release day! 🎉We just shipped v2 Core Framework 2.5.0, Analyzers 1.2.0, and Visual Studio adapter 2.5.0. This release includes a bunch of quality of life improvements, bug fixes, and an overhauled assertion library that includes new assertions, new overloads, and much better (and most consistent) assertion failure messages.Enjoy!Release notes:<a href="https://xunit.net/releases/v2/2.5.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/v2/2.5.0</a> <a href="https://xunit.net/releases/analyzers/1.2.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/analyzers/1.2.0</a> <a href="https://xunit.net/releases/visualstudio/2.5.0" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://xunit.net/releases/visualstudio/2.5.0</a><a href="https://fosstodon.org/tags/dotnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dotnet</a> <a href="https://fosstodon.org/tags/csharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#csharp</a> <a href="https://fosstodon.org/tags/fsharp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fsharp</a> <a href="https://fosstodon.org/tags/unittest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittest</a> <a href="https://fosstodon.org/tags/tdd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tdd</a>

Ed SuominenWriting a <a href="https://hachyderm.io/tags/UnitTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTest</a> for each significant piece of my <a href="https://hachyderm.io/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> code is a pain in the ass. Sometimes it feels like I spend most of my <a href="https://hachyderm.io/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> time writing test code instead of the stuff I actually want.But then I add a feature or optimize something and debugging is as simple as making various tests pass again and I’m glad to have invested all that time in the parallel universe of a well-built test suite.It’s like wearing an N95 during a pandemic, except for your code instead of your brain.

Recent searches

Search options

Administered by:

Server stats:

#unittest