Naulius

3 ms·

1.
Stop bashing bugs – they're undesirable states, not villains(testflows.com)
2 points by Naulius 5mo ago|0 comments
2.
Testing Super Mario Using a Behavior Model Autonomously – Finding Real Bugs(testflows.com)
1 points by Naulius 5mo ago|0 comments
3.
Writing Test Programs, Not Just Tests – Going Beyond the Test Runner(testflows.com)
1 points by Naulius 6mo ago|1 comments
4.
by Naulius 6mo ago
Most test frameworks follow a "runner mentality"; you write test functions and hand them to a runner that controls discovery, execution order, and flow. The moment you need something dynamic (loop a test N times based on a runtime
5.
by Naulius 7mo ago
When writing the articles in that series, the focus was more on getting the technical ideas and details right, not on spelling, grammar and text flow in which LLMs excel. That specific section "Why this maps to Genetic Algorithms?&quot
6.
by Naulius 7mo ago
An LLM was used to help polish the text, and that section probably got over-polished. The ideas and code are authentic. The article is intentionally detailed for those who want the full reasoning, but you can always skip straight to the sou
7.
by Naulius 7mo ago
Agree. However, the described technique isn't really AI, there's no neural network or training. It's GA-driven exploration for testing: mutate inputs, keep what gets you further down the state space, discard what doesn't
8.
by Naulius 7mo ago
Thanks! You're right that there's a resemblance to RL. The original approach was proposed by Antithesis, and in Part 1 we map it more directly to a mutation-based Genetic Algorithm: stored paths are the population, the x-position
9.
Testing Super Mario Using a Behavior Model Autonomously(testflows.com)
29 points by Naulius 7mo ago|9 comments
10.
by Naulius 7mo ago
We built an autonomous testing example that plays Super Mario Bros. to explore how behavior models combine with autonomous testing. Instead of manually writing test cases, it systematically explores the game's massive state space while