
pytest
SoftwareWikipedia
11
MENTIONS
7
EPISODES
7
PODCASTS
Search complete. 11 mentions across 7 episodes found for "pytest".
Sep 8, 2026
The Safe Way to Ship Production Code Written by AI Agents
H
9:00HackerNoon AINARRATOR
But be honest with your team about what tests pass actually proves, which on current evidence is less than most people assume.
H
9:08HackerNoon AINARRATOR
METR published an analysis in March 2026, where maintainers from three real open-source projects, Scikit-learn, Sphinx, and Pytest, reviewed two hundred and ninety-six AI-generated pull requests thought that already passed SWE-bench verified, a standard benchmark for coding agents.
H
9:25HackerNoon AINARRATOR
Roughly half of those test-passing PRs would not have been merged into the real codebase.
H
9:31HackerNoon AINARRATOR
The maintainers' reasons weren't nitpicks: core functionality failures, code that broke other parts of the system, and straightforward code quality problems the test suite had no way to catch.
#495 Banned
C
8:32Calvin Hendryx-ParkerHOST
Verification matters more.
C
8:34Calvin Hendryx-ParkerHOST
You see right here, PyTest, 45%.
C
8:37Calvin Hendryx-ParkerHOST
So we see lots more testing happening, which I think is also a very good sign.
C
8:41Calvin Hendryx-ParkerHOST
And I'll talk a little bit about that in my second article as well.
Claude Code’s Inline Output Buffers Slash Tool Round Trips
L
0:13Lachlan ReidHOST
tax.
L
0:14Lachlan ReidHOST
I cannot tell you how many times I've stared at my terminal in the shed watching Claude run PyTest, hit that old 4,000 character wall, write a temp file, and then burn a whole extra turn just going, oh, let me read that file for you.
J
0:28James TurnerHOST
It was so frustrating.
J
0:30James TurnerHOST
Every single build error or stack trace over 4,000 characters forced that extra read tool call round trip.
2025 FOSS4G NA | Taming Dependency Hell - Thomas Machler
T
8:56Thomas MachlerGUEST
They will always be there.
T
9:01Thomas MachlerGUEST
And then here, for example, I have my development environment where I need additional libraries like PyTest and PyTest coverage and whatever.
T
9:10Thomas MachlerGUEST
And I can then say, okay, this is my default environment and then also add in the test environment or the dependencies that I specify in the test feature.
T
9:22Thomas MachlerGUEST
And here you see this is the solve group.
T
10:11Thomas MachlerGUEST
You can just say, I always set log level to debug.
T
10:14Thomas MachlerGUEST
It's just a random thing I just picked.
T
10:17Thomas MachlerGUEST
Whenever I'm checking out the the deaf environment, and then I want to define my tasks, which are tied to the deaf environment, and this would be test, where I'm running PyTest with certain arguments, and then the test CI, which I want to run only on my CI runner, and then I want to use different arguments for this, for example.
T
10:39Thomas MachlerGUEST
And then I can run pixi run eDevTest or eDevTestCI and it will then execute these different command line commands for me.
Your AI Memory Should Be Markdown Files
H
8:12Herman PoppleberryHOST
Inside that, you'd have markdown files for persistent preferences.
H
8:16Herman PoppleberryHOST
I use PyTest for testing.
H
8:18Herman PoppleberryHOST
I prefer type hints everywhere.
H
8:19Herman PoppleberryHOST
Here are the libraries I reach for by default, that kind of thing.
Episode 396 - AI & Code with Simon Willison
A
1:32AmitHOST
He did.
A
1:32AmitHOST
He explicitly told it to use red-green test-driven development and PyTest.
A
1:38AmitHOST
That means the agent has to write a failing test first, then write the code to make it pass.
Y
1:44YuvalHOST
That seems like a very deliberate choice to keep the agent grounded.
Y
2:06YuvalHOST
Are those tests running against all three database engines?
S
2:10speaker_2UNKNOWN
They are.
S
2:11speaker_2UNKNOWN
He told it to use PyTest fixtures, which is a standard pattern in the Python ecosystem for running the same test against multiple backends.
S
2:19speaker_2UNKNOWN
Because PyTest is so well established, the agents understand exactly how to implement those fixtures.
P
Unknown podcast
GitHub - genlayerlabs/genlayer-project-boilerplate
Aug 19 · 2 Mentions
S
0:49speaker_0NARRATOR
The repository structure looks like this.
S
0:51speaker_0NARRATOR
a contracts directory that holds the Python intelligent contracts, a tests directory with a direct subdirectory for fast in-memory tests, and an integration subdirectory for full end-tone tests, a frontend directory that contains the Next.js application, a deploy directory that stores TypeScript deployment scripts, a configuration file for the test runner, a pyprojectoml for Python and PyTest configuration, and a GitHub workflows directory that contains the CI pipeline.
S
1:19speaker_0NARRATOR
To get started, first set up a Python virtual environment, activate it, and install the required packages with pip.
S
1:25speaker_0NARRATOR
Next, run the genvm linter on the football bets contract.
S
1:29speaker_0NARRATOR
The linter checks for forbidden imports, uses of non-deterministic calls, invalid storage types such as treemap or dynarray, missing decorators, absent return type annotations, and operations that occur outside equivalence principal blocks.
S
1:44speaker_0NARRATOR
It also enforces over 20 other rules.
S
1:47speaker_0NARRATOR
Direct mode tests are run with PyTest.
S
1:49speaker_0NARRATOR
They deploy contracts in memory, allow you to specify the transaction sender, and mock HTTP requests or LLM calls so you get instant feedback.