• over_clox@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    Sounds like a new fancy term for what’s already called fuzzing, but with more modern AI duct taped on.

  • El Barto@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    Why is this garbage in a science community?

    Where’s the study? The experiments? The research?

  • str82L @lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    Agreed. This project is currently about validating the test coverage/power. It’s not too much of a stretch to envisage it one day actually designing/writing the tests themselves, but this is only a first step. And if it did end up creating tests and also editing the code under test, would there not be an independence issue?

      • str82L @lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        If the same entity is both writing the code and testing the code it’s not great. Even though the code in this instance is there to support testing, it’s still being crafted by an ai that may one day also be expanded to create the tests themselves. It’s that scenario I’m concerned about. It’s part of the reason we do more than just unit test.

        • El Barto@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          4 months ago

          Hm, but isn’t usually the same developer who writes the code and the test?

          Why would it be an issue if an AI does the same?

          • str82L @lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            4 months ago

            Developers write and execute the unit test, and perhaps component test. Once you get past that to system testing it should be someone independent.