flexiberry
Open-source, Lightweight HTTP client & API testing framework
Start new thread

flexiberry - Open-source, Lightweight HTTP client & API testing framework

byā€¢
FlexiBerry is an open-source, lightweight HTTP client and API testing framework built for developers. Chain dependent API requests, validate responses, manage environments, and automate workflows with the intuitive Berry scripting language. Available as a modern Web app, CLI, and IDE extensions, FlexiBerry makes API testing faster, more readable, maintainable, and seamless for local development and CI/CD pipelines.

Add a comment

Replies

Best
Maker
šŸ“Œ
šŸ‘‹ Hi Product Hunt! I'm the solo developer behind FlexiBerry. I built FlexiBerry because I wanted an API testing tool that was lightweight, developer-friendly, and easy to maintain. As projects grow, API testing often becomes difficult to manage with complex UIs and bulky collections. I wanted something that felt more like writing code than configuring a tool. That's why I created .berry, a simple scripting language for writing readable and maintainable API tests. FlexiBerry lets you chain dependent requests, validate responses, manage environments, and automate API workflows. It's available as a web app, CLI, and Open VSX extensions, so you can use it wherever you prefer to work. FlexiBerry is completely open source, and I'm actively building it in public. Your feedback will directly influence the roadmap, whether it's feature requests, bug reports, or ideas to improve the developer experience. If you find it useful, Iā€™d really appreciate it if you could ā­ the GitHub repository ā€” it helps a lot with visibility and motivates continued development. If you give it a try, I'd love to know: What feature is missing? What would make you switch from your current API testing tool? How can FlexiBerry better fit your workflow? Thank you for checking out FlexiBerry and supporting open source! šŸš€

honestly the Berry scripting language is kind of genius, way more readable than my usual setup. chained a few dependent requests in the CLI in under five minutes

Maker

Ā thank you for your valuable feedback.

Looks great, especially the Berry scripting idea. One thing that would really help me is built-in diffing between response payloads across environments, so you can instantly spot when staging drifts from prod. Could even tie it into the test runner to fail on unexpected diffs.

Maker

Thanks for the feedback, That's definitely doable. Let me explore the best way to implement it in the Berry script. Since each environment execution is isolated, we need to find a simple and clean approach to compare or validate the results from two separate executions.

Tried chaining a few requests with the Berry scripting and the syntax actually stayed readable instead of turning into a wall of JSON. Also nice that the same scripts run in the CLI without changes.

Maker

Ā thank you for yourfeedback.

Honestly the Berry scripting language is a nice touch, makes chaining dependent requests way more readable than a wall of json. Going to try it in our CI pipeline this week.

Maker

Ā thankyou for the feedback