💬 Contribute & Feedback

💬 Contribute & Feedback

Whether you're testing distributed systems, designing asynchronous flows, or integrating @fizzwiz/mockchain into real projects — your feedback helps shape a better way to test one node at a time.

🤝 How You Can Contribute

  • Share feedback – Found something unclear, elegant, or missing? Tell us!
  • Suggest improvements – From API design to docs clarity, ergonomics, or testing strategy — every suggestion matters.
  • Submit examples – Real-world testing scenarios help others see how to use MockChain effectively.
  • Report bugs – Open a GitHub issue with a minimal reproduction. Even small reports make a big difference.

👉 GitHub Issues: https://github.com/fizzwiz/mockchain/issues

🙋 Why Your Feedback Matters

@fizzwiz/mockchain is still evolving — built for developers who care about clarity and control in async testing. Your insights help refine how developers write, test, and reason about distributed node behavior. Together, we can make testing simpler, more expressive, and more predictable.

💡 Have an Idea?

Is there another async abstraction that could benefit from mockability? Do you envision MockChain integrating with a specific framework or testing tool? Start a discussion or open a proposal — ideas aligned with @fizzwiz’s spirit of intuitiveness are always welcome.

❤️ Sponsor the Project

If this library helps you ship faster or test better, consider supporting its continued development. Your sponsorship sustains thoughtful, minimalistic open-source tools like @fizzwiz/mockchain.

💖 GitHub Sponsors: https://github.com/sponsors/fizzwiz

🙏 Thanks for being part of the journey.
— @fizzwiz ✨


Comments

Post a Comment

Popular posts from this blog

🔑 Why MockChain Is a Chain

🔑 Why   MockChain   Is a Chain When testing asynchronous methods, you often want to   control behavior without rewriting the method logic .   MockChain   allows you to inject and observe behavior at   any point in a promise chain , not just at the start. 🧩 Two Ends of the Chain Consider a typical async method: function fetchData ( url, opts, autoStart = true ) { return MockChain . fromResponse (url, opts, autoStart) . then ( res => res. json ()) . then ( obj => obj. ok ); } There are   three promises   involved: Root node ( root )   — the initial wrapped promise (e.g.,   fetch() ) resolving to a Response object. Mid node   — the in-between promise resolving to the JSON object. Leaf node ( end )   — the last node resolving to a Boolean flag. In tests, you usually mock the   root   to trigger the   end   manually: const chain = fetchData ( undefined , undefined , false ); // don’t awai...
Read more

🏁 The autostart Flag

🏁 The   autostart   Flag — Designing Testable Async Methods Async functions are convenient, but they hide execution inside native Promises — which can’t be intercepted or mocked. To preserve control, every asynchronous method in a distributed system should expose a   autostart   flag . This simple addition enables you to decide   when   asynchronous execution actually happens, giving your tests full deterministic control while keeping production behavior untouched. 🎯 The Idea Instead of rewriting async logic for testing, let each function decide whether to execute its asynchronous flow immediately or defer it. A   mockable method : Runs normally in production ( autostart = true ). Defers execution in tests ( autostart = false ), allowing   MockChain   to intercept and control outcomes. ⚙️ Implementation Pattern import { MockChain } from '@fizzwiz/mockchain' ; /** * Fetch data from a URL. * @param { string } url * @param { boolean ...
Read more

⚠️ Async Functions Are Not Mockable

  ⚠️ Async Functions Are Not Mockable Async functions are convenient in JavaScript, but they are   incompatible with mockable Promises   like   MockChain . This post explains   why   async functions break mockability and how to preserve control over promise chains. ❌ Why Async Functions Break Mockability An   async   function always returns a   native Promise , even if you return another Promise (as a   MockChain ) inside it. async function example ( ) { const chain = MockChain . resolve ( 42 ); return chain; // You think you're returning a MockChain... } const result = example (); console . log (result instanceof MockChain ); // ❌ false Why this happens:   ECMAScript’s   Promise assimilation   wraps any thenable in a new native Promise, so the original instance is lost. Consequences: Custom subclass methods ( .mock() ,   .fail() ,   .root ,   .parent ) disappear. Any attached metadata ( promise...
Read more