home.social

#integrationtesting — Public Fediverse posts

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

fetched live
  1. Blog - Shared Postgres Test Container with Expecto in FSharp

    I’m learning FSharp by creating a web application. I’ve cycled through lots of different ways of doing things, libraries, etc. Today I finally got my integration tests to use a single docker test contaner with the Expecto test framework. I couldn’t find a good example online of how to do it, so I’m sharing it here.

  2. Stop losing hours to unrealistic mocks.

    Flaky CI, brittle stubs, heavy virtualization - sound familiar?

    Mocktail fixes this:
    🎥 Record real responses once
    ▶️ Replay forever inside your test suite

    Fast, reliable, realistic integration tests for Java teams.

    👉 Read more: squads.com/blog/youre-losing-h
    #JavaTesting #IntegrationTesting

  3. The testing pyramid advocates for a balanced approach with many fast unit tests at the base, fewer integration tests in the middle, and a minimal set of end-to-end tests at the top to ensure reliable and efficient bug detection.

    dev.to/hongster85/unit-vs-inte

  4. The testing pyramid advocates for a balanced approach with many fast unit tests at the base, fewer integration tests in the middle, and a minimal set of end-to-end tests at the top to ensure reliable and efficient bug detection.

    #UnitTesting #IntegrationTesting #EndToEndTesting

    dev.to/hongster85/unit-vs-inte

  5. Testing #APIs ≠ mocking a class. Integration bugs hide in configs, headers, and serialization quirks. Marián Varga shows how @WireMockOrg & REST Assured make #Java integration tests real.

    Learn how: javapro.io/2025/08/06/java-has

    #IntegrationTesting #WireMock #RestAssured #JAVAPRO

  6. Testing #APIs ≠ mocking a class. Integration bugs hide in configs, headers, and serialization quirks. Marián Varga shows how @WireMockOrg & REST Assured make #Java integration tests real.

    Learn how: javapro.io/2025/08/06/java-has

    #IntegrationTesting #WireMock #RestAssured #JAVAPRO

  7. One of the things a good CMake-powered C++ library should do is to test its own integration - in other words, if others can plug it into their projects. One reason is obvious - nobody will use your library if they can't. The second one is pragmatic - the tests act as documentation for the users.

    I've spent many hours refining my integration testing of CMake code, and I've compiled my learnings into the following article:
    medium.com/@nerudaj/cmake-inte

    I've also fallen into the inevitable rabbit hole of dependency management in CMake, so if you want to learn about that, the article has you covered as well! 😵‍💫

    What do you think? Are there other aspects of integration that are worth testing? And would you be interested in an article on how to make findable prebuilt packages with CMake?

    #cpp #cmake #integrationtesting

  8. One of the things a good CMake-powered C++ library should do is to test its own integration - in other words, if others can plug it into their projects. One reason is obvious - nobody will use your library if they can't. The second one is pragmatic - the tests act as documentation for the users.

    I've spent many hours refining my integration testing of CMake code, and I've compiled my learnings into the following article:
    medium.com/@nerudaj/cmake-inte

    I've also fallen into the inevitable rabbit hole of dependency management in CMake, so if you want to learn about that, the article has you covered as well! 😵‍💫

    What do you think? Are there other aspects of integration that are worth testing? And would you be interested in an article on how to make findable prebuilt packages with CMake?

  9. APIs testen ≠ eine Klasse mocken. Integrationsfehler stecken in Konfiguration, Headern & Serialisierung. Marián Varga zeigt, wie @WireMockOrg & REST Assured echte Integrationstests in #Java ermöglichen.

    Lese: javapro.io/de/java-verbindet-s

    #IntegrationTesting #WireMock #RestAssured

  10. APIs testen ≠ eine Klasse mocken. Integrationsfehler stecken in Konfiguration, Headern & Serialisierung. Marián Varga zeigt, wie @WireMockOrg & REST Assured echte Integrationstests in #Java ermöglichen.

    Lese: javapro.io/de/java-verbindet-s

    #IntegrationTesting #WireMock #RestAssured

  11. 🚀 Unveil the Power of the NixOS Integration Test Driver! In Part 1 of our series, we dive deep into this incredible tool that's changing the game in DevOps and software testing. From orchestrating multiple VMs to running GUI apps with text recognition, discover how it simplifies integration testing and saves you precious time and resources.

    Developers and system administrators, this one's for you! In a world where efficiency and reliability are paramount, the NixOS Integration Test Driver combines the best of declarative configuration, virtualization, and Python scripting. It's a hidden gem within the NixOS ecosystem that's set to revolutionize the way we test and validate our systems.

    Whether you're a seasoned NixOS enthusiast or new to this innovative operating system, fasten your seatbelts as we venture into a world where integration testing becomes an effortless and integral part of your development and deployment process.

    In this article, you'll explore:
    ✅ Minimal requirements: Accessible to a wide range of developers with just a Linux system and KVM support.
    ✅ Effortless debugging: Run tests locally for debugging when integration tests fail in your CI pipeline.
    ✅ Speed and reliability: Unparalleled framework for creating robust tests that don't flake.
    ✅ Realistic simulations: Closely simulate actual customer deployments, enhancing your ability to catch issues before they reach production.

    Stay tuned for Part 2, where we'll dive even deeper into the NixOS Integration Test Driver!

    ➡️ nixcademy.com/2023/10/24/nixos

    #NixOS #DevOps #Testing #SoftwareDevelopment #IntegrationTesting

  12. @marcorossignoli I noticed that you're one of the main contributors on Coverlet.

    I created this [issue](github.com/coverlet-coverage/c) because I'm getting 0% coverage for code executed by integration tests using WebApplicationFactory.

    The issue seems to be specific to my solution because I created a minimum solution and the coverage worked (linked in my latest comment).

    Do you know what might be going wrong?

    Any help would be greatly appreciated.

    #dotnet #coverlet #integrationtesting

  13. @marcorossignoli I noticed that you're one of the main contributors on Coverlet.

    I created this [issue](github.com/coverlet-coverage/c) because I'm getting 0% coverage for code executed by integration tests using WebApplicationFactory.

    The issue seems to be specific to my solution because I created a minimum solution and the coverage worked (linked in my latest comment).

    Do you know what might be going wrong?

    Any help would be greatly appreciated.

    #dotnet #coverlet #integrationtesting

  14. Vandaag in de Eerste Kamer: Software testing. Het AcICT bespreekt de bevindingen over het "integraal ketentesten" van het digitale stelsel bij de omgevingswet. eerstekamer.nl/commissievergad

    #omgevingswet #AcICT #SoftwareTesting #IntegrationTesting #EersteKamer

  15. #AutomatedTesting is often blocked due to some well-known issues, especially in a microservices architecture. API and service simulators can eliminate five common issues that block test automation:
    ➡️ Issue 1: APIs or services not yet available
    ➡️ Issue 2: Slow or manual processes in backend or third-party systems
    ➡️ Issue 3: Test data issues
    ➡️ Issue 4: Set up hypothetical scenarios for error scenario testing
    ➡️ Issue 5: Third-party API and service restrictions

    Find out more in this #InfoQ article by Wojciech Bulaty: bit.ly/3IR3eD8

    #SoftwareArchitecture #API #IntegrationTesting

  16. is often blocked due to some well-known issues, especially in a microservices architecture. API and service simulators can eliminate five common issues that block test automation:
    ➡️ Issue 1: APIs or services not yet available
    ➡️ Issue 2: Slow or manual processes in backend or third-party systems
    ➡️ Issue 3: Test data issues
    ➡️ Issue 4: Set up hypothetical scenarios for error scenario testing
    ➡️ Issue 5: Third-party API and service restrictions

    Find out more in this article by Wojciech Bulaty: bit.ly/3IR3eD8

  17. Check out our video on testing. We talk about getting the most out of your tests and avoiding the pitfalls that drag on many teams and distract teams from the goal of building quality software.

    #Flutter and #iOS devs in particular will find this interesting. We talk about full app widget testing

    #flutterdev #unittesting #integrationtesting #e2etesting

    youtu.be/3dKugGP0LAc

  18. Check out our video on testing. We talk about getting the most out of your tests and avoiding the pitfalls that drag on many teams and distract teams from the goal of building quality software.

    #Flutter and #iOS devs in particular will find this interesting. We talk about full app widget testing

    #flutterdev #unittesting #integrationtesting #e2etesting

    youtu.be/3dKugGP0LAc

  19. At work I specialize in #developerproductivity. I work in simulation at #Waymo. Before that I worked on #staticanalysis (Tricorder) and #integrationtesting (Guitar) at Google. Before that I was a PhD student at #NYU where I contributed to CVC4.

    I am not a believer in methodologies or best practices. I just do what I do and try not to mess up too often.

    #introductions

  20. At work I specialize in #developerproductivity. I work in simulation at #Waymo. Before that I worked on #staticanalysis (Tricorder) and #integrationtesting (Guitar) at Google. Before that I was a PhD student at #NYU where I contributed to CVC4.

    I am not a believer in methodologies or best practices. I just do what I do and try not to mess up too often.

    #introductions