Runabout

Instantly reproduce scenarios in your code

48 followers

Instantly reproduce scenarios in your code

48 followers

Visit website

AI Coding Agents

•

Testing and QA software

Runabout is a plugin for the IntelliJ IDE that allows Java developers to run any method in their project without writing tests or running their entire project. It serves as a new way to reproduce issues, debug high priority bugs, and test new code.

Free Options

Launch tags:Software Engineering•Developer Tools•Artificial Intelligence

Launch Team

Framer AI AgentsDesign and publish professional sites with AI

Promoted

Runabout

Maker

📌

Hey Everyone! This is my first time ever posting on Product Hunt. I'm excited to share Runabout with you after several weeks of hard work! Runabout lets developers run targeted parts of their code. It serves as a new way to debug issues and test code. The idea came to me while I was working on a Java project and had a thought: "Wait, why can't I just run this specific piece of code?" It seemed silly to write a whole new test class or run the entire application when I only had a few lines of code to debug. Runabout is currently only available for IntelliJ IDEA (community and ultimate) and only supports Java development. Some features: - Run any method in isolation: public, private, static, etc... - Run methods in a running JVM. Useful for accessing database connections, caches, and static "global" variables. - Use an LLM to help run it for you (free, optional) Coming soon: - Shared parameters across teams - Support for other IDEs - Support for other Languages If you're a Java developer, I hope Runabout can save you time and effort. Any feedback is greatly appreciated. Thank you!

Report

3yr ago

tambo

Very cool. I wonder if you could have it auto-save any run as a test case to be repeated later? Could be an interesting way to write tests in general

Report

3yr ago

Runabout

Maker

@milst That's a good idea! Right now Runabout will temporarily store your most recent parameters so you can repeatedly run them, but they're not guaranteed to persist forever. Would you find it useful to be able to tag "runs" and label them for future use?

Report

3yr ago

tambo

@ethanwbond Tags could be cool, but I was thinking about something like building up a local "test" file. I guess behind the scenes for each run you build some kind of "calling method" where you create the input params, and call the "running method". The calling method could be appended to a file so that later I could re-run all my built "calling methods" at once. I guess you'd have to add a field to let users specify expected output of a run. Details might get a little complicated...

Report

3yr ago

Runabout

Maker

@milst I see, that's interesting. What you're describing sounds like a hybrid between traditional Junit testing and the manual running that Runabout does. I like it - I think in general it would be best to give more customization power to users for stuff like that. Also assertions, pre/post execution methods, etc..

Report

3yr ago