I have two suggestions for the Test Balloon IDE pl...

# testballoon

[Eugen Martynov]

I have two suggestions for the Test Balloon IDE plugin (if it is possible):
1. Support CMD+T shortcut - jumping between code and test
2. For action "Create new test" have option for Test Ballon and template for it
Good one for the ticket on the GitHub?

[Oliver.O]

I have thought about these. While both are well established in the old world of manually written code and restrictive class/method-based unit tests, I wonder if they'd be widely used in the age of GenAI and given the flexibility of TestBalloon. What do you think?

[Eugen Martynov]

I do jump between test and code. I almost never use test creation template. Point2 just to be on pair.

[Oliver.O]

To what extent can we expect to have a 1:1 relationship between a certain type of code and the corresponding test? We'd need to assume a structural correspondence and a specific type of naming for the test, right?

[Eugen Martynov]

Yeah, I think this is how it works - tries to match class name in test class name

[Oliver.O]

So what we could potentially have is
1. Go to test: From (inside) a main source class MC, search for TestBalloon's top-level properties approximately matching the name of MC.
2. Go to test subject: From (inside) a top-level TestBalloon test suite TS, search for top-level classes approximately matching the name of TS.
And building on 1. we could also add the possibility to create at least a test source file with a corresponding empty top-level suite.

What seems impractical is trying to navigate between a main function (top level or as a class method) and a specific test. There would be too much variation in structure.

Does that fit the bill? Anything else?

[Eugen Martynov]

I have habbit - use CMD+T to switch between test and source. I don't think there is navigate from place in source to specific test.

[Eugen Martynov]

If plugin has 1 and 2 that would be close how I use it. I don't know internals of IDE - if you need to navigate to specific line or you can just open file and keep the state of scroll there how it was before.

[Oliver.O]

So I'll just create an issue with the mechanism I just outlined. The IDE has lots of integration points for stuff like that, so the main effort is to find the right ones.

Fun fact: For JUnit, there is an "intention" which creates a primitive test from a primitive function. It does not really make sense as I see it:

[phldavies]

"Create new test" still feels relevant as a mechanical option for initial boilerplate/structure (even if it just automates creating a suitable named top level suite / test) as the idea of using AI tokens/energy to do so never sits right. That said, I don't use it often and the api is so very lean for TestBalloon testballoon

[Oliver.O]

Yeah, I guess the main savings would be not having to create the test source file at the correct location.