AI Is Writing Your Tests, yet Nothing Is Getting Tested
If you ask a general AI model for a test and it knows nothing about your testing infrastructure, It will fill the gaps with plausible guesses: an invented endpoint, an assumed clean environment, a mocked dependency it could not see. The result fails in one of two directions. Either the test breaks for reasons that have nothing to do with your app and an engineer spends the afternoon fixing generated code. Or worse, it passes while testing nothing, asserting against its own assumptions. AI Test Creation in Testkube generates the other way around: from your workflows, your environments, and your execution history, in the framework your team already uses, run in your real infrastructure within seconds and kept as code in your repository. In this session, Ole Lensmar, CTO of Testkube, makes the argument and proves it live. You will see: A test generated in plain language, in a real framework, and run in a real cloud environment. How generated tests become code you own: synced to your Git repository. How created tests plug into the rest of the platform, so they are orchestrated, executed, and visible alongside everything you already run How to get started today. If you are using AI to generate code, and wonder how can you efficiently test it in the same infrastructure it lives, all within the same platform, this one is for you. Register now!
Hacker News (AI / LLM) files mainly under ai. We currently carry 7,341 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Wistia |
| Canonical URL | https://testkube.wistia.com/live/events/uswa35zy9l |
| Publication time | Fri, 02 Oct 2026 13:05:25 +0000 |
| Retrieval time | 2026-10-02T13:21:35.761Z |
| Last seen | 2026-10-02T13:21:35.761Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher description |
| Excerpt method | Publisher-supplied description / RSS summary field. |
| Summary | None yet |
| Summary source text | description |
| Citation coverage | No WeSearch summary has been generated for this story yet. |
| Cluster | v-48IkWqHs-h · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Discussion
0 commentsMore from Wistia
