[LTP] LTP old API conversion

Li Wang liwang@redhat.com
Wed Mar 18 06:18:07 CET 2026


On Tue, Mar 17, 2026 at 04:32:30PM +0100, Cyril Hrubis wrote:
> Hi!
> > .. and tests conversion for tests which are smaller than 200 lines of code
> > requires minimal (if no) edit. I will continue to adapt the ltp-convert skill
> > in order to tweak and to improve this process for bigger tests.
> 
> I would disagree here withe the minimal edit. The old tests are quite
> often garbage. So the human in the process should asses if the test is
> actually doing anything useful and guide the machine to implement better
> test in a case that the original wasn't doing anything useful.
> 
> > ~~ Said so..
> > 
> > .. since this process seems to be quite straight forward, and with the usage
> > of LLM we could easily generate hundreds of patches per month, we don't really
> > want to flood the ML with garbage and to overwhelm who's involved into
> > maintenance review.
> 
> I'm pretty sure that you will get this down to smaller set as long as
> you actually spend some time thinking about what the test does. At least
> for me I'm able to spend 30% time on a test conversion because LLM, but
> you have to spend some time understanding what the test does and making
> sure it makes sense. Otherwise it's garbage in - garbage out.

Yes but not entirely. We can have AI summarize test methods within
code comments, which helps us grasp the underlying logic much faster
than reading through legacy code directly.

And, nowdays AI is gradually becoming the producer of code, while
humans(specifically maintainers) assume the role of the ultimate
guardians of code quality.

-- 
Regards,
Li Wang



More information about the ltp mailing list