HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
testflows
Examples
Python2026–2026
testflows / Examples

Examples

Examples using TestFlows.com Open-source Testing Framework

Testing & Quality
Explore on GitHubRead Hacker News discussions
3Distinct people
3Mentions
0Explicit recommenders
4GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Examples using TestFlows.com Open-source Testing Framework

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 10:02:42 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval3 dated mentions

Observed mentions: 2026-02-19 20:21:44 UTC to 2026-02-24 19:01:08 UTC.

012026-02-19 18:00:00 UTC to 2026-02-20 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 19, 18:002026-02-20 00:00:00 UTC to 2026-02-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-20 06:00:00 UTC to 2026-02-20 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-20 12:00:00 UTC to 2026-02-20 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-20 18:00:00 UTC to 2026-02-21 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-02-21 00:00:00 UTC to 2026-02-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 06:00:00 UTC to 2026-02-21 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 12:00:00 UTC to 2026-02-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 18:00:00 UTC to 2026-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 00:00:00 UTC to 2026-02-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 06:00:00 UTC to 2026-02-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 22, 06:002026-02-22 12:00:00 UTC to 2026-02-22 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 18:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 00:00:00 UTC to 2026-02-23 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 06:00:00 UTC to 2026-02-23 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 12:00:00 UTC to 2026-02-23 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 18:00:00 UTC to 2026-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-24 00:00:00 UTC to 2026-02-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-24 06:00:00 UTC to 2026-02-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-24 12:00:00 UTC to 2026-02-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-24 18:00:00 UTC to 2026-02-25 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 24, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 19, 18:002026-02-19 18:00:00 UTC2026-02-20 00:00:00 UTC110
Feb 20, 00:002026-02-20 00:00:00 UTC2026-02-20 06:00:00 UTC000
Feb 20, 06:002026-02-20 06:00:00 UTC2026-02-20 12:00:00 UTC000
Feb 20, 12:002026-02-20 12:00:00 UTC2026-02-20 18:00:00 UTC000
Feb 20, 18:002026-02-20 18:00:00 UTC2026-02-21 00:00:00 UTC101
Feb 21, 00:002026-02-21 00:00:00 UTC2026-02-21 06:00:00 UTC000
Feb 21, 06:002026-02-21 06:00:00 UTC2026-02-21 12:00:00 UTC000
Feb 21, 12:002026-02-21 12:00:00 UTC2026-02-21 18:00:00 UTC000
Feb 21, 18:002026-02-21 18:00:00 UTC2026-02-22 00:00:00 UTC000
Feb 22, 00:002026-02-22 00:00:00 UTC2026-02-22 06:00:00 UTC000
Feb 22, 06:002026-02-22 06:00:00 UTC2026-02-22 12:00:00 UTC000
Feb 22, 12:002026-02-22 12:00:00 UTC2026-02-22 18:00:00 UTC000
Feb 22, 18:002026-02-22 18:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 23, 00:002026-02-23 00:00:00 UTC2026-02-23 06:00:00 UTC000
Feb 23, 06:002026-02-23 06:00:00 UTC2026-02-23 12:00:00 UTC000
Feb 23, 12:002026-02-23 12:00:00 UTC2026-02-23 18:00:00 UTC000
Feb 23, 18:002026-02-23 18:00:00 UTC2026-02-24 00:00:00 UTC000
Feb 24, 00:002026-02-24 00:00:00 UTC2026-02-24 06:00:00 UTC000
Feb 24, 06:002026-02-24 06:00:00 UTC2026-02-24 12:00:00 UTC000
Feb 24, 12:002026-02-24 12:00:00 UTC2026-02-24 18:00:00 UTC000
Feb 24, 18:002026-02-24 18:00:00 UTC2026-02-25 00:00:00 UTC101

What Hacker News says

1 sources
vzakaznikov·Feb 24, 2026
Learn how a behavior model combined with autonomous testing helped us find interesting bugs in our reference Super Mario game implementation. The model validates every frame during exploration, but when it disagrees with the game, which one is wrong? This is bidirectional testing: the model tests the game, and the game tests the model. The process uncovered several real engine bugs, including a teleport bug in Level 4 where Mario gets snapped across the screen due to overlapping collision boxes. All code is open source: https://github.com/testflows/Examples/tree/v3.0/SuperMario
In Testing Super Mario Using a Behavior Model Autonomously – Finding Real Bugs

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.