Veganism Social

Brian AllbeeImplementing first part of the third layer in of the <a href="https://mastodon.social/tags/PACT" class="mention hashtag" rel="nofollow noopener" target="_blank">#PACT</a> testing processes in a standard <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> framework: Prescribing (requiring) a standard test-method structure/set for functions.<a href="https://goblinfish-code.blogspot.com/2025/04/the-pact-for-functions.html" rel="nofollow noopener" translate="no" target="_blank">https://goblinfish-code.blogspot.com/2025/04/the-pact-for-functions.html</a>

Brian AllbeeThe last of my catch-up posts, moving them from LinkedIn to Blogger: Implementing the next layer in of the <a href="https://mastodon.social/tags/PACT" class="mention hashtag" rel="nofollow noopener" target="_blank">#PACT</a> testing processes in a standard <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> framework: Prescribing (requiring) a test-module for each source module.<a href="https://goblinfish-code.blogspot.com/2025/04/the-pact-for-module-members.html" rel="nofollow noopener" translate="no" target="_blank">https://goblinfish-code.blogspot.com/2025/04/the-pact-for-module-members.html</a>

Brian AllbeeContinuing to move LinkedIn articles to Blogger posts: Implementing the first layer of the <a href="https://mastodon.social/tags/PACT" class="mention hashtag" rel="nofollow noopener" target="_blank">#PACT</a> testing processes in a standard <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> framework: Prescribing (requiring) a test-module for each source module.<a href="https://goblinfish-code.blogspot.com/2025/04/the-pact-for-test-modules.html" rel="nofollow noopener" translate="no" target="_blank">https://goblinfish-code.blogspot.com/2025/04/the-pact-for-test-modules.html</a>

Brian AllbeeContinuing to move LinkedIn articles to Blogger posts: The first in a series of articles capturing my thoughts and efforts with respect to improving the reliability of <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>.<a href="https://goblinfish-code.blogspot.com/2025/04/prescribing-active-contract-testing.html" rel="nofollow noopener" translate="no" target="_blank">https://goblinfish-code.blogspot.com/2025/04/prescribing-active-contract-testing.html</a>

Tuvoc TechnologiesA Comprehensive Guide to the Top 7 Python Testing Frameworks<a href="https://www.tumblr.com/webappinsights/780978087921844224/a-comprehensive-guide-to-the-top-7-python-testing" rel="nofollow noopener" translate="no" target="_blank">https://www.tumblr.com/webappinsights/780978087921844224/a-comprehensive-guide-to-the-top-7-python-testing</a>Explore the top 7 Python testing frameworks that ensure code reliability, efficiency, and maintainability. This guide helps developers choose the right tools to streamline their testing process in 2025.<a href="https://mastodon.social/tags/PythonTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#PythonTesting</a> <a href="https://mastodon.social/tags/TestingFrameworks" class="mention hashtag" rel="nofollow noopener" target="_blank">#TestingFrameworks</a> <a href="https://mastodon.social/tags/PythonDevelopers" class="mention hashtag" rel="nofollow noopener" target="_blank">#PythonDevelopers</a> <a href="https://mastodon.social/tags/SoftwareTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoftwareTesting</a> <a href="https://mastodon.social/tags/AutomationTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#AutomationTesting</a> <a href="https://mastodon.social/tags/PythonTools" class="mention hashtag" rel="nofollow noopener" target="_blank">#PythonTools</a> <a href="https://mastodon.social/tags/QA" class="mention hashtag" rel="nofollow noopener" target="_blank">#QA</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://mastodon.social/tags/Python2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python2025</a> <a href="https://mastodon.social/tags/TestAutomation" class="mention hashtag" rel="nofollow noopener" target="_blank">#TestAutomation</a> <a href="https://mastodon.social/tags/CodeQuality" class="mention hashtag" rel="nofollow noopener" target="_blank">#CodeQuality</a> <a href="https://mastodon.social/tags/DevTools" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevTools</a> <a href="https://mastodon.social/tags/CleanCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#CleanCode</a> <a href="https://mastodon.social/tags/PyTest" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyTest</a> <a href="https://mastodon.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</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 Pro Max⚡️- Tarrifed🚀 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>

Brian AllbeeImplementing the first layer of the <a href="https://mastodon.social/tags/PACT" class="mention hashtag" rel="nofollow noopener" target="_blank">#PACT</a> testing processes in a standard <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> framework: Prescribing (requiring) a test-module for each source module.<a href="https://www.linkedin.com/feed/update/urn:li:activity:7317501915712405504" rel="nofollow noopener" translate="no" target="_blank">https://www.linkedin.com/feed/update/urn:li:activity:7317501915712405504</a>

Brian AllbeeAs I'm between jobs (again), I'm writing code for my own purposes, and writing about writing that code.On LinkedIn, for professional visibility: capturing my thoughts and efforts with respect to improving the reliability of <a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a>.<a href="https://www.linkedin.com/pulse/goblinfish-testing-pact-000-prescribing-active-contract-brian-allbee-eza4c" rel="nofollow noopener" translate="no" target="_blank">https://www.linkedin.com/pulse/goblinfish-testing-pact-000-prescribing-active-contract-brian-allbee-eza4c</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>

Victor on Software🚀 Speed up your Go test suite (and your CI)! 🧪💨 Tired of waiting forever for your tests to finish in CI? 😩 You're not alone.Check out our latest guide on parallelizing large Go test suites to drastically cut down CI cycle times. 🕒⚡️✅ Split your test suite ✅ Run tests in parallel with GitHub Actions ✅ Real-world Makefile + GitHub Actions examples included!👉 Read it now: <a href="https://victoronsoftware.com/posts/large-go-test-suite/" rel="nofollow noopener" translate="no" target="_blank">https://victoronsoftware.com/posts/large-go-test-suite/</a><a href="https://techhub.social/tags/Golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Golang</a> <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://techhub.social/tags/DeveloperExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeveloperExperience</a> <a href="https://techhub.social/tags/ContinuousIntegration" class="mention hashtag" rel="nofollow noopener" target="_blank">#ContinuousIntegration</a>

Joche OjedaTesting SignalR Applications with Integration Tests<a href="https://www.jocheojeda.com/2025/04/02/testing-signalr-applications-with-integration-tests/" rel="nofollow noopener" translate="no" target="_blank">https://www.jocheojeda.com/2025/04/02/testing-signalr-applications-with-integration-tests/</a><a href="https://mastodon.social/tags/SignalR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SignalR</a> <a href="https://mastodon.social/tags/TDD" class="mention hashtag" rel="nofollow noopener" target="_blank">#TDD</a> <a href="https://mastodon.social/tags/IntegrationTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#IntegrationTesting</a> <a href="https://mastodon.social/tags/DotNET" class="mention hashtag" rel="nofollow noopener" target="_blank">#DotNET</a> <a href="https://mastodon.social/tags/ASPNETCore" class="mention hashtag" rel="nofollow noopener" target="_blank">#ASPNETCore</a> <a href="https://mastodon.social/tags/TestServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#TestServer</a> <a href="https://mastodon.social/tags/ChatTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#ChatTesting</a> <a href="https://mastodon.social/tags/WebSockets" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebSockets</a> <a href="https://mastodon.social/tags/RealTimeApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#RealTimeApps</a> <a href="https://mastodon.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://mastodon.social/tags/APITesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#APITesting</a> <a href="https://mastodon.social/tags/CSharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSharp</a> <a href="https://mastodon.social/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://mastodon.social/tags/TestDrivenDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#TestDrivenDevelopment</a>

TechGeeksApparelDo You Even Unit Test, Bro? Real devs test their code… or at least claim they do! Tag that one dev who "tests in production." 🔗 <a href="https://techgeeksapparel.com/do-you-even-unit-test-bro-t-shirt/" rel="nofollow noopener" translate="no" target="_blank">https://techgeeksapparel.com/do-you-even-unit-test-bro-t-shirt/</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://mastodon.social/tags/QAEngineer" class="mention hashtag" rel="nofollow noopener" target="_blank">#QAEngineer</a> <a href="https://mastodon.social/tags/BugSquasher" class="mention hashtag" rel="nofollow noopener" target="_blank">#BugSquasher</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>

dorotaCIntegration <a href="https://fosstodon.org/tags/tests" class="mention hashtag" rel="nofollow noopener" target="_blank">#tests</a> are annoying, but what they helped me fix would have been even more annoying to debug raw.Perhaps I made an annoying code base :F<a href="https://fosstodon.org/tags/unittesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittesting</a> <a href="https://fosstodon.org/tags/coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#coding</a> <a href="https://fosstodon.org/tags/debugging" class="mention hashtag" rel="nofollow noopener" target="_blank">#debugging</a>

DjumakaI'm unit testing a method relying on a private method to fetch some data. I want to mock that other method so I have consistent data (or in this case, avoid DB calls) but this looks like a rocket science. Theory is everywhere "you should not alter your class for the sake of testing it" and this is a real indicator that this class is badly constructed (architectural issue). But this is the case for 50% of web... so I have to do stupid thing to test old code <a href="https://phpc.social/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#php</a> <a href="https://phpc.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnitTesting</a> <a href="https://phpc.social/tags/mock" class="mention hashtag" rel="nofollow noopener" target="_blank">#mock</a>

RJ"Keeping tests valuable: Avoid implementation details!" <a href="https://thepragmaticengineer.hashnode.dev/keeping-tests-valuable-avoid-implementation-details" rel="nofollow noopener" translate="no" target="_blank">https://thepragmaticengineer.hashnode.dev/keeping-tests-valuable-avoid-implementation-details</a> <a href="https://fosstodon.org/tags/unittesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittesting</a> <a href="https://fosstodon.org/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwaredevelopment</a> <a href="https://fosstodon.org/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#development</a> <a href="https://fosstodon.org/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸If you use feature flags your automated tests are worthless unless you run them against every possible combination of feature flags.<a href="https://mastodon.social/tags/developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#developer</a> <a href="https://mastodon.social/tags/software" class="mention hashtag" rel="nofollow noopener" target="_blank">#software</a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#development</a> <a href="https://mastodon.social/tags/dev" class="mention hashtag" rel="nofollow noopener" target="_blank">#dev</a> <a href="https://mastodon.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwaredevelopment</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.social/tags/softwareengineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareengineering</a> <a href="https://mastodon.social/tags/engineering" class="mention hashtag" rel="nofollow noopener" target="_blank">#engineering</a> <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webDev</a> <a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> <a href="https://mastodon.social/tags/AutomatedTests" class="mention hashtag" rel="nofollow noopener" target="_blank">#AutomatedTests</a> <a href="https://mastodon.social/tags/tdd" class="mention hashtag" rel="nofollow noopener" target="_blank">#tdd</a> <a href="https://mastodon.social/tags/unittesting" class="mention hashtag" rel="nofollow noopener" target="_blank">#unittesting</a> <a href="https://mastodon.social/tags/tests" class="mention hashtag" rel="nofollow noopener" target="_blank">#tests</a> <a href="https://mastodon.social/tags/featureFlag" class="mention hashtag" rel="nofollow noopener" target="_blank">#featureFlag</a> <a href="https://mastodon.social/tags/feature" class="mention hashtag" rel="nofollow noopener" target="_blank">#feature</a> <a href="https://mastodon.social/tags/flag" class="mention hashtag" rel="nofollow noopener" target="_blank">#flag</a>

Rachel BrindleAlready filed my first issue: The Test struct needs a public initializer. There's a workaround so that I can keep going, but it uses something that's explicitly marked as only for the Test macro.<a href="https://github.com/apple/swift-testing/issues/521" rel="nofollow noopener" translate="no" target="_blank">https://github.com/apple/swift-testing/issues/521</a><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>

Rachel BrindleImplementing this resultBuilder-based Testing DSL in public: <a href="https://github.com/Quick/Quick/pull/1292" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Quick/Quick/pull/1292</a><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>

Recent searches

Search options

Administered by:

Server stats:

#unittesting

Recent searches

Search options

Administered by:

Server stats:

unitTesting

#unittesting