home.social

#unittest — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #unittest, aggregated by home.social.

  1. Adam Johnson :django: :python: @adamchainz ·

    🧪 I just released unittest-parametrize 1.9.0.

    This package helps you make parametrized tests that work with the grain of unittest, but can still be run with pytest.

    This release adds new skip/expected_failure features, fixes a bug when using Coverage.py's dynamic contexts, and tidies up error messages and usage docs.

    github.com/adamchainz/unittest

    #python #unittest
  2. xUnit.net @[email protected] ·

    Based on this poll, we will be removing support for Visual Studio 2019 and out-of-support versions of Visual Studio 2022 from `xunit.analyzers` sometime before the final 2.0.0 release.

    dotnet.social/@xunit/116350131

    #DotNet #Roslyn #Analyzer #CSharp #UnitTest

    #dotnet #roslyn #analyzer #csharp #unittest
  3. Jan :rust: :ferris: @[email protected] ·

    @shuttle I consequently use #TDD, where possible.

    Yes, sure, #Rust prevents a lot of bugs at compile time already, but not logic bugs.

    For example in #CSVDiff 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):
    github.com/jqnatividad/qsv/iss

    csv-diff:
    gitlab.com/janriemer/csv-diff

    In the future I'd like to add property and mutation testing as well 🤓

    #RustLang #Testing #UnitTest

    #tdd #rust #csvdiff #rustlang #testing #unittest
  4. Jan :rust: :ferris: @[email protected] ·

    And this is why #UnitTests and #TDD are awesome/necessary (even in #Rust/ #RustLang):

    The original requirement:
    figure out how many columns the _result_ of diffing two CSVs in #CsvDiff have.

    Do you see the error-pattern?

    It's
    - when we have no diff
    &&
    - at least one CSV has headers

    which 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!?🥰

    #SoftwareEngineering #UnitTest

    #rustlang #unittests #tdd #rust #csvdiff #softwareengineering
  5. Juhis @[email protected] ·

    Eric makes a good argument for why you should write integration tests first in a new project, before unit and end to end tests.

    #testing #unittest #integrationtest #python #programming #webdev

    mostlypython.substack.com/p/do

    #testing #unittest #integrationtest #python #programming #webdev
  6. DocRekd @[email protected] ·

    @SecurityWriter #CI all the things with #nix .
    This includes automatic #unitTest and #integrationTest before merging

    #ci #nix #unittest #integrationtest
  7. Ed Howland @edhowland ·

    @podfeet @bbusschots wow! It just blew up when I did an integration test.
    But I wrote solid unit test. There must be something that has to do with loading a file using the source command and maybe at overwrites some variables. Still researching it.

    #bash #programmingbystealth #getopts #unittest #integrationtest #pbs149
  8. Ænðr E. Feldstraw @[email protected] ·

    Proud #software #developer is proud.

    The day before yesterday I implemented an algorithm to calculate an authorization proof.

    Yesterday I tested it successfully to recreate a known proof. #unitTest

    Today I used it successfully to authenticate a request and download some data. #integrationTest

    That's always the hardest part when communicating with third parties.

    #integrationtest #unittest #developer #software