Remix.run Logo
▲ joegibbs 2 hours ago

They made a blog post to announce that they’d written thirteen unit tests? Sure, there’s value in handmade software and all that but GIMP is not really a particularly excellent piece of software - if anything was to benefit from unleashing the agents it would be GIMP.

▲raincole 2 hours ago | parent | next [-]

It'd be really interesting to look back the comparison between projects with strict non-AI policies (e.g. GIMP) and ArtCraft in 2027.

My personal prediction is that ArtCraft will blow all the old non-AI projects in similar fields out of the water and GIMP will be remembered as a thing of the past. But if I got proven wrong I'd be happy too: at least we will know the value of non-AI policies.

▲flexagoon 23 minutes ago | parent [-]

GIMP is far from the best FOSS image editor for many use cases. IMO for many simple editing tasks that people usually need unless they're professional photo editors, even Inkscape, a primarily vector editor, is a better photo editor than GIMP.

▲raincole 19 minutes ago | parent [-]

Inkscape is what made me believe ArtCraft would be the clear winner, btw. It's very hard to imagine using Inkscape ever again since I tried VectorCraft. (And I'm fully aware that some Path Effects can only be done quickly in Inkscape.)

▲qtqtqt 2 hours ago | parent | prev | next [-]

They must have set up a reusable harness, and it's the most important part.

▲Jolter 2 hours ago | parent | prev | next [-]

I’d go so far as to say that in general, adding tests for legacy software before a refactor or rewrite is the perfect time to put the agent to work.

▲plant-ian an hour ago | parent | prev | next [-]

It sounds like they are nearly end to end user interface (UI) tests, not just unit tests.

▲WD-42 2 hours ago | parent | prev | next [-]

Did you read the article? These aren’t unit tests. They are UI tests which are pretty hard to do well with desktop apps.

▲qtqtqt 2 hours ago | parent [-]

Especially given it isn't as easy as using Cypress.

▲slopinthebag 2 hours ago | parent | prev | next [-]

we forget, but before AI this would have been at least 6 months of work, at least 50 meetings, and at least 7 separate sprints.

▲altmanaltman 2 hours ago | parent | prev | next [-]

The blog article doesn't say they have written thirteen unit tests.

> *GIMP already has unit tests*. A unit test checks one small part of the code, for example how GIMP reads an XCF file. But our unit tests were not opening a real window. So it coult not tell us if a dialog opens, or if a menu item did its job.

> Note that GIMP *already had tests of GUI code*, usually interacting directly with the core code, and sometimes even simulating input devices’ events (pointer movements, clicks, drags…). But nothing can beat interacting with the real interface. Furthermore such legacy tests directly hijacking core code come with their own problems, such as breaking all too often (and not because they detected a bug), all while not being able to detect whole categories of bugs.

> UI tests check the program as a whole, in the same way as you use it.

▲hulitu 2 hours ago | parent | prev [-]

> if anything was to benefit from unleashing the agents

AI can write tests now ? For its own software ? Can it evaluate the results ? Correctly ? /s

▲aidenialislife 2 hours ago | parent [-]

Writing tests never was the hard part of the job anyway.