home.social

#mocks — Public Fediverse posts

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

fetched live
  1. Wenn du mit Java Tests schreibst, stößt du ziemlich schnell auf ein Problem: Deine Klasse arbeitet oft nicht allein. Sie ruft andere Klassen auf, spricht vielleicht mit einer Datenbank, nutzt eine externe API oder verschickt Nachrichten. Genau an der Stelle kommt Mockito ins Spiel.

    magicmarcy.de/java-testen-mit-

    #Mockito #Test #Coding #Java #Mocks #Abhängigkeiten #JUnit #Programming

  2. Ich kann jetzt sagen, ich bin mit einem publizierten* Autor** verheiratet.

    heise.de/hintergrund/Flexibel-

    * bei heise.de
    ** von genau einem Fachartikel

    #heise #programming #mocks

  3. Ich kann jetzt sagen, ich bin mit einem publizierten* Autor** verheiratet.

    heise.de/hintergrund/Flexibel-

    * bei heise.de
    ** von genau einem Fachartikel

    #heise #programming #mocks

  4. Frontend и OpenAPI: генерация клиента, мокирование API и данных с помощью MSW

    Генерация кода по спецификации OpenAPI и мокирование запросов - эффективный способ автоматизировать процессы разработки и решить некоторые специфические задачи. В статье описано применение различных инструментов, которые могут быть использованы при генерации и мокировании.

    habr.com/ru/companies/nauka/ar

    #openapi #msw #mocks #typescript

  5. Тестируемый код в Golang

    Когда я вижу очередную статью или видеоурок про тестирование кода, я почти уверен, что мне опять расскажут про моки. Создаётся впечатление, что это самый лучший и правильный способ писать тесты, и вообще, невозможно обойтись без моков. Это не так! Можно писать тестируемый код без моков. Более того, использование моков следует избегать и использовать их только в специфичных случаях.

    habr.com/ru/companies/skbkontu

    #go #golang #mocks #mocking #mock #тестирование #тесты #tdd

  6. Backend-for-Frontend (BFF): решение проблемы взаимодействия фронтенда и бэкенда

    В современной разработке веб-приложений одной из ключевых проблем является несовместимость между фронтендом и бэкендом. Фронтенд-команды часто вынуждены ждать, пока бэкенд предоставит необходимые API, а бэкенд-разработчики тратят время на адаптацию логики под изменения в интерфейсе. Это приводит к задержкам в разработке, сложностям в тестировании и постоянным несоответствиям в данных. Что такое Backend-for-Frontend (BFF)? Backend-for-Frontend (BFF) — это архитектурный паттерн, который помогает устранить разрыв между фронтендом и бэкендом. BFF выступает промежуточным слоем, который адаптирует данные и логику бэкенда под нужды конкретного фронтенда. Это позволяет фронтенд-командам работать с API сразу, а бэкенд-разработчикам подключать логику по мере готовности, что значительно ускоряет процесс разработки и снижает количество доработок.

    habr.com/ru/articles/880964/

    #frontendразработка #backendразработка #javascript #expressjs #node #bff #mocks #api

  7. @fazzaro Really nice article, thanks for sharing it!

    It has been a few years now since I began to think that dynamic #mocks really get in the way of #refactoring by really coupling the tests with the implementation.

    I like how the author points out how they are breaking encapsulation and the solution he offers to address the problem.

    I'm a bit skeptical about the scalability of that solution though, and that's the reason I still use mocking frameworks, but try to rely on them the least I can. But hey, I'll try his approach on a small project soon, and see what comes out of it!

  8. @fazzaro Really nice article, thanks for sharing it!

    It has been a few years now since I began to think that dynamic really get in the way of by really coupling the tests with the implementation.

    I like how the author points out how they are breaking encapsulation and the solution he offers to address the problem.

    I'm a bit skeptical about the scalability of that solution though, and that's the reason I still use mocking frameworks, but try to rely on them the least I can. But hey, I'll try his approach on a small project soon, and see what comes out of it!

  9. "You need tests that don't break when you refactor. When you use dynamic mocks, tests tend to fail whenever you make changes in SUTs. Even though you have tests, they don't enable refactoring."

    #softwareengineering #softwarearchitecture #tdd #unittests #mocks #testdoubles

    blog.ploeh.dk/2022/10/17/stubs

  10. "You need tests that don't break when you refactor. When you use dynamic mocks, tests tend to fail whenever you make changes in SUTs. Even though you have tests, they don't enable refactoring."

    #softwareengineering #softwarearchitecture #tdd #unittests #mocks #testdoubles

    blog.ploeh.dk/2022/10/17/stubs

  11. "You need tests that don't break when you refactor. When you use dynamic mocks, tests tend to fail whenever you make changes in SUTs. Even though you have tests, they don't enable refactoring."

    #softwareengineering #tdd #fakes #vs #mocks

    blog.ploeh.dk/2022/10/17/stubs

  12. "You need tests that don't break when you refactor. When you use dynamic mocks, tests tend to fail whenever you make changes in SUTs. Even though you have tests, they don't enable refactoring."

    #softwareengineering #tdd #fakes #vs #mocks

    blog.ploeh.dk/2022/10/17/stubs

  13. 🔥 Microcks 1.10.0 is released! 🚀

    It's packed with unique features:
    🌟 Stateful #mocks support for even smarter behavior
    💡 New lightweight #API Examples spec format
    🎁 Uber and
    @graalvm
    native distros enhancements
    🚨 Install dependencies updates

  14. 🔥 Microcks 1.10.0 is released! 🚀

    It's packed with unique features:
    🌟 Stateful #mocks support for even smarter behavior
    💡 New lightweight #API Examples spec format
    🎁 Uber and
    @graalvm
    native distros enhancements
    🚨 Install dependencies updates

  15. 📦 Microcks @quarkusio Dev Service version 0.2.4 is out! Grab it while it's hot! 🔥

    It provides live reloads of your @openapi, @AsyncAPISpec, @graphql and @Grpc schemas to always have fresh #mocks!

    🙏 Romain Quinio, for the great idea!

    github.com/microcks/microcks-q

  16. 📦 Microcks @quarkusio Dev Service version 0.2.4 is out! Grab it while it's hot! 🔥

    It provides live reloads of your @openapi, @AsyncAPISpec, @graphql and @Grpc schemas to always have fresh #mocks!

    🙏 Romain Quinio, for the great idea!

    github.com/microcks/microcks-q

  17. 📦 The new 0.2.7 release of our Microcks #Testcontainers #Java module is out! 🔥

    You can now directly import full repository snapshots 📸 with tons of #mocks from a single source of truth!

    github.com/microcks/microcks-t

  18. 📦 The new 0.2.7 release of our Microcks #Testcontainers #Java module is out! 🔥

    You can now directly import full repository snapshots 📸 with tons of #mocks from a single source of truth!

    github.com/microcks/microcks-t

  19. How do you write #UnitTests for #dotNET? Join us for #Cleveland C# User Group where we'll discuss ".NET #Testing #BestPractices". It's a #NoSlides talk where we take an #IoT project and write tests, #refactoring along the way, and learning about #mocks. Join us: meetup.com/cleveland-csug/even, code: github.com/robrich/net-testing.

  20. How do you write #UnitTests for #dotNET? Join us for #Cleveland C# User Group where we'll discuss ".NET #Testing #BestPractices". It's a #NoSlides talk where we take an #IoT project and write tests, #refactoring along the way, and learning about #mocks. Join us: meetup.com/cleveland-csug/even, code: github.com/robrich/net-testing.

  21. If people actually read “XUnit Test Patterns: Refactoring Test Code” by G. Meszaros maybe they’d understand what test doubles are, or when/why to use them. Maybe they wouldn’t write how they hate “mocks”, but focused on merits of their approach.

    There’s so much misunderstanding and non-constructive criticism in our profession. I really admire those few people I know who strive to write from a positive angle. I’m not sure if I’d be able to doit.

    #testing #mocks #notrealymocks #testdoubles #tdd