Welcome to ignite-test Discussions!

[0xjcf]

We’re thrilled to announce igniteTest, a lightweight and extensible testing framework designed to make testing state-driven logic and web components easier than ever.

While we’re still in the planning phase, we want to hear from you—developers who work with Redux, XState, and MobX. Your feedback will help shape igniteTest into a tool that meets your needs.

---

🌟 Why igniteTest?

Here’s what we’re aiming for:

• Unified API: One syntax for testing Redux, XState, and MobX.
• Effortless State Validation: Built-in support for assert, pending, resolve, and reject.
• Flexible Workflows:
  • Use state for isolated, self-contained tests.
  • Use E2E workflows to validate state progression.

---

📣 How You Can Help

This is your chance to help shape igniteTest from the ground up. Let us know:

• What challenges do you face when testing state-driven logic?
• What features would make igniteTest a must-have for your projects?
• How do you currently test state-driven libraries like Redux, XState, or MobX?

Your input will directly influence the development of igniteTest.

---

💻 What’s Next?

Here’s our roadmap:

• Phase 1: Core development supporting XState, Redux, and MobX.
• Phase 2: Integration with ignite-element for web component testing.
• Phase 3: Reporting tools, CLI support, and automated performance logging.

---

Join the conversation, and let’s make testing better together. 🚀

🔗 Get involved here: GitHub Discussions
⭐ Star the repo to stay updated: igniteTest Repository Link