Shakedown Social

0 posts0 participants0 posts today

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 noreferrer" 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 noreferrer" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a>

Ramin Honary<a href="https://www.well-typed.com/blog/2023/04/falsify/%20" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#tech</a> <a class="hashtag" href="https://fe.disroot.org/tag/software" rel="nofollow noopener noreferrer" target="_blank">#software</a> <a class="hashtag" href="https://fe.disroot.org/tag/haskell" rel="nofollow noopener noreferrer" target="_blank">#haskell</a> <a class="hashtag" href="https://fe.disroot.org/tag/welltyped" rel="nofollow noopener noreferrer" target="_blank">#WellTyped</a> <a class="hashtag" href="https://fe.disroot.org/tag/quickcheck" rel="nofollow noopener noreferrer" target="_blank">#QuickCheck</a> <a class="hashtag" href="https://fe.disroot.org/tag/unittesting" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a> <a class="hashtag" href="https://fe.disroot.org/tag/propertytesting" rel="nofollow noopener noreferrer" target="_blank">#PropertyTesting</a>

Uli Kusterer (Not a kitteh)Protip: If you have test data in your C++ unit tests that needs to be passed into some C API, be consistent and declare it as vector<uint8_t> testData, and always call testData.size() on it, not sizeof(testData) like you do elsewhere for C-style arrays of uint8_t testData[].<a href="https://chaos.social/tags/CPlusPlus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPlusPlus</a> <a href="https://chaos.social/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> <a href="https://chaos.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://chaos.social/tags/unitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unitTesting</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 noreferrer" 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 noreferrer" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/swift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swift</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/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/swift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swift</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/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a>

Aral BalkanQuick heads up: I just deprecated @small-tech/tape-with-promises (for adding promise support to Tape 4.x).<a href="https://www.npmjs.com/package/@small-tech/tape-with-promises" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.npmjs.com/package/@small-tech/tape-with-promises</a>Tape version 5.x supports promises so my little module is no longer necessary unless you’re stuck on v4.x.What’s tape? A neat little JavaScript unit testing framework I like:<a href="https://github.com/tape-testing/tape" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/tape-testing/tape</a>Already use tape? Does your test runner need more monkeys and bananas? Try my tap-monkey module:<a href="https://codeberg.org/small-tech/tap-monkey#readme" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/small-tech/tap-monkey#readme</a>🙊🍌<a href="https://mastodon.ar.al/tags/tape" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tape</a> <a href="https://mastodon.ar.al/tags/nodeJS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nodeJS</a> <a href="https://mastodon.ar.al/tags/unitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unitTesting</a> <a href="https://mastodon.ar.al/tags/tapMonkey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tapMonkey</a>

JuanluElGuerre :verified:🚀 Ready to master unit testing in .NET? Learn how to use <a href="https://hachyderm.io/tags/xUnit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xUnit</a>, <a href="https://hachyderm.io/tags/NSubstitute" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NSubstitute</a>, and <a href="https://hachyderm.io/tags/AutoFixture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AutoFixture</a> in this step-by-step guide with HangfireDemoApi. From mocking to background tasks, we’ve got you covered! Read more 👉 <a href="https://wp.me/p29SK-Wy" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://wp.me/p29SK-Wy</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a> <a href="https://hachyderm.io/tags/DotNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DotNet</a> <a href="https://hachyderm.io/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developers</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸<a href="https://linuxrocks.online/@haircode" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@haircode</a> <a href="https://mastodon.social/tags/typescript" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#typescript</a> <a href="https://mastodon.social/tags/tailwind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tailwind</a> <a href="https://mastodon.social/tags/reactRouter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reactRouter</a> <a href="https://mastodon.social/tags/docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#docker</a> <a href="https://mastodon.social/tags/graphql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#graphql</a> <a href="https://mastodon.social/tags/java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#java</a> <a href="https://mastodon.social/tags/nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nix</a> <a href="https://mastodon.social/tags/vim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vim</a> <a href="https://mastodon.social/tags/mac" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mac</a> <a href="https://mastodon.social/tags/ios" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ios</a> <a href="https://mastodon.social/tags/iphone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iphone</a> <a href="https://mastodon.social/tags/express" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#express</a> <a href="https://mastodon.social/tags/gcp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gcp</a> <a href="https://mastodon.social/tags/reactNative" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#reactNative</a> <a href="https://mastodon.social/tags/nativeApps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nativeApps</a> <a href="https://mastodon.social/tags/appStore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#appStore</a> <a href="https://mastodon.social/tags/apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apple</a> <a href="https://mastodon.social/tags/aapl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aapl</a> <a href="https://mastodon.social/tags/htmx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#htmx</a> <a href="https://mastodon.social/tags/vercel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vercel</a> <a href="https://mastodon.social/tags/netlify" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#netlify</a> <a href="https://mastodon.social/tags/heroku" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#heroku</a> <a href="https://mastodon.social/tags/nevernester" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nevernester</a> <a href="https://mastodon.social/tags/10xDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#10xDev</a> <a href="https://mastodon.social/tags/10xdevelopers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#10xdevelopers</a> <a href="https://mastodon.social/tags/codeReview" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#codeReview</a> <a href="https://mastodon.social/tags/pairProgramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pairProgramming</a> <a href="https://mastodon.social/tags/oop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oop</a> <a href="https://mastodon.social/tags/earlyReturns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#earlyReturns</a> <a href="https://mastodon.social/tags/guardClauses" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#guardClauses</a> <a href="https://mastodon.social/tags/flutter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#flutter</a> <a href="https://mastodon.social/tags/angular" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#angular</a> <a href="https://mastodon.social/tags/neverNesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#neverNesting</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/unitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unitTesting</a> <a href="https://mastodon.social/tags/cssFrameworks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cssFrameworks</a> <a href="https://mastodon.social/tags/jest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jest</a> <a href="https://mastodon.social/tags/jetbrains" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jetbrains</a> <a href="https://mastodon.social/tags/neoVim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#neoVim</a> <a href="https://mastodon.social/tags/wordpress" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wordpress</a> <a href="https://mastodon.social/tags/SQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SQL</a> <a href="https://mastodon.social/tags/postgresql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#postgresql</a> <a href="https://mastodon.social/tags/rdbms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rdbms</a> <a href="https://mastodon.social/tags/rubyOnRails" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rubyOnRails</a>

RJ"Keeping tests valuable: Avoid implementation details!" <a href="https://thepragmaticengineer.hashnode.dev/keeping-tests-valuable-avoid-implementation-details" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#unittesting</a> <a href="https://fosstodon.org/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#softwaredevelopment</a> <a href="https://fosstodon.org/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://fosstodon.org/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" target="_blank">#developer</a> <a href="https://mastodon.social/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#software</a> <a href="https://mastodon.social/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#development</a> <a href="https://mastodon.social/tags/dev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dev</a> <a href="https://mastodon.social/tags/softwaredevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#softwaredevelopment</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://mastodon.social/tags/softwareengineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#softwareengineering</a> <a href="https://mastodon.social/tags/engineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#engineering</a> <a href="https://mastodon.social/tags/webDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webDev</a> <a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a> <a href="https://mastodon.social/tags/AutomatedTests" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AutomatedTests</a> <a href="https://mastodon.social/tags/tdd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tdd</a> <a href="https://mastodon.social/tags/unittesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittesting</a> <a href="https://mastodon.social/tags/tests" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tests</a> <a href="https://mastodon.social/tags/featureFlag" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#featureFlag</a> <a href="https://mastodon.social/tags/feature" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#feature</a> <a href="https://mastodon.social/tags/flag" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" 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 noreferrer" 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 noreferrer" target="_blank">#SwiftLang</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a>

Manuel LandesfeindHive mind, do you employ (unit) testing in data analysis scripts? If so, how and what are your best practices? We frequently develop packages with unit testing. But equally often write "run-once" analysis scripts/notebooks. Those often contain functions and (more often) assumptions on loaded data but we rarely test/check these. This is something to improve but I wonder how others handle this.<a href="https://genomic.social/tags/RStats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RStats</a> <a href="https://genomic.social/tags/rmarkdown" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rmarkdown</a> <a href="https://genomic.social/tags/testthat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testthat</a> <a href="https://genomic.social/tags/assertthat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assertthat</a> <a href="https://genomic.social/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://genomic.social/tags/jupyter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#jupyter</a> <a href="https://genomic.social/tags/unittesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unittesting</a> <a href="https://genomic.social/tags/datascience" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datascience</a> <a href="https://genomic.social/tags/bioinformatics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bioinformatics</a>

Rachel BrindleWoo! I’m so excited to announce I’ll be presenting at One More Thing conf during WWDC week!I’ll be talking about testing, and specifically about testing SwiftUI and Swift concurrency!I’ll also be a “floating expert” there on testing in general.Hope to see you there!<a href="https://hachyderm.io/tags/Swift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Swift</a> <a href="https://hachyderm.io/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SwiftUI</a> <a href="https://hachyderm.io/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a> <a href="https://hachyderm.io/tags/OMTConf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OMTConf</a>

carlyn“The best time to build a test was before the first commit. The next best time is now.” – Proverbious the Commitor, probably<a href="https://www.whynotestflight.com/excuses/hello-usd-part-13-test-test-test/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.whynotestflight.com/excuses/hello-usd-part-13-test-test-test/</a><a href="https://mastodon.social/tags/XCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XCode</a> <a href="https://mastodon.social/tags/XCTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XCTest</a> <a href="https://mastodon.social/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SwiftLang</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a> <a href="https://mastodon.social/tags/Equatable" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Equatable</a>

Todd A. Jacobs | Rubyist<a href="https://ruby.social/@davetron5000" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@davetron5000</a> In what way are you differentiating this from <a href="https://ruby.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a> or functional testing? I agree you should never have to test core Ruby or Rails features, but doesn't a view test exercise whatever you're bumping against here?

Brad WilsonFeeling a bit confused by my decision making in <a href="https://fosstodon.org/@xunit" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@xunit</a>.This passes:`Assert.Equal(42, 42L);`This fails:`Assert.Equivalent(42, 42L);`That feels wrong. It's either backward, or both should pass. Equivalent was designed to be the "less strict" version of things, so why did I decide that equal values of different intrinsic types were a failure?Equal has passed for 15 years. Equivalent is relatively new. I'm leaning towards both passing.What do you think I should do?<a href="https://mastodon.social/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a> <a href="https://mastodon.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a>

Jon Reid💞 Why did I become obsessed with <a href="https://iosdev.space/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a> for iOS? Here's what makes me tick <a href="https://qualitycoding.org/podcast-ios-unit-testing-champion/" rel="nofollow noopener noreferrer" target="_blank">https://qualitycoding.org/podcast-ios-unit-testing-champion/</a> <a href="https://iosdev.space/tags/ExtremeProgramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ExtremeProgramming</a>

Duncan BabbageSure wish there was a decent way to create parameterized <a href="https://iosdev.space/tags/XCTest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XCTest</a> unit tests. I've got an array of test data, want to run the same method on each of about ten items and assert that a particular outcome occurs. Found this approach but too much of a kludge for me: <a href="https://kazaimazai.com/parametrized-xctest-swift/" rel="nofollow noopener noreferrer" target="_blank">https://kazaimazai.com/parametrized-xctest-swift/</a>Not sure whether to just duplicate ten tests, one for each test data item, or to put a for...in in an XCTest and deal with the lack of specificity for failures. Hgn. <a href="https://iosdev.space/tags/Swift" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Swift</a> <a href="https://iosdev.space/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a>

Sid :ve:(My <a href="https://techhub.social/tags/introduction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#introduction</a> reposted from a previous instance)I'm Siddarth, a <a href="https://techhub.social/tags/SoftwareEngineer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineer</a> in India. Love discussing <a href="https://techhub.social/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#software</a>, <a href="https://techhub.social/tags/SoftwareCraftsmanship" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareCraftsmanship</a>, <a href="https://techhub.social/tags/UnitTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UnitTesting</a> and <a href="https://techhub.social/tags/SoftwareArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareArchitecture</a>. I mainly use <a href="https://techhub.social/tags/Java" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Java</a> and <a href="https://techhub.social/tags/Kotlin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Kotlin</a>, though I'm looking to learn <a href="https://techhub.social/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rust</a> soon, likely on my weekday <a href="https://techhub.social/tags/Twitch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Twitch</a> streams. Usually highly opinionated on things I care about 😁I also enjoy <a href="https://techhub.social/tags/books" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#books</a>, <a href="https://techhub.social/tags/anime" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#anime</a> and <a href="https://techhub.social/tags/manga" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#manga</a>; I'll toot more about those whenever I come across anything interesting. Drop me a follow if you'd like!

Recent searches

Search options

Administered by:

Server stats:

#unittesting