home.social

#integrationtesting — Public Fediverse posts

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

  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. 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.

  3. 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.

  4. 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.

  5. 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

  6. 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

  7. 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

  8. 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

  9. 🛠️ Nhiều dev nhảy vào framework mà chưa hiểu lý do test thất bại. Bài viết chia sẻ nền tảng kiểm thử: unit vs integration vs end‑to‑end, cách làm test có giá trị, những anti‑pattern thường gặp và cách test tăng tốc độ phát triển lâu dài. Bạn lần đầu nào “bật sáng” về kiểm thử? #testing #unitTesting #integrationTesting #e2e #dev #pháttriển #kiểmthử

    reddit.com/r/programming/comme

  10. 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

  11. 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

  12. 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

  13. 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

  14. 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

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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?

  21. 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

  22. 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

  23. Working a new side project at the moment and it has again hammered home the benefit of having a thorough test suite.

    Sure the tests may be repetitive and a chore to write, but I've already uncovered numerous small bugs in my back-end API that I did not know about... Mostly small things like a missing "await" or a missing decorator stopping a dependency from being injected correctly.

    #softwaredevelopment #softwaretesting #testing #nodejs #TsED #integrationtesting