What’s the one JSON problem that slows you down the most?

by•

As testers and engineers, we probably spend more time with JSON than we realize.

While building Captain JSON, we kept finding ourselves opening different tools for formatting, validation, comparison, JSONPath, conversion, JWTs, and large JSON files.

So we're curious:

What does your actual JSON workflow look like?

What tools do you use today, and where does the workflow become frustrating?

We're building Captain JSON for engineers, QA professionals, SDETs, and developers, and we'd love to build the next features around real-world problems rather than assumptions.

Tell us what you wish existed. 👇

5 views

Add a comment

Replies

Be the first to comment