The Go gopher was designed by Renée French. https://gotalk.connpass.com/event/388084/
Figuring out how to trust AI-written code faster is the project of software engineering for the next few years, IMO.We'll need to figure out the techniques and strategies that let us merge AI code sight unseen. Some ideas that have already started floating around: - Include the spec for the change in your PR and only bother reviewing that, on the assumption that the AI faithfully executed it - Lea
I'm Building Agents That Run While I Sleep I Have No Idea If What They Ship Is Any Good I've been building agents that write code while I sleep. Tools like Gastown run for hours without me watching. Changes land in branches I haven't read. A few weeks ago I realized I had no reliable way to know if any of it was correct: whether it actually does what I said it should do. I've run Claude Code works
We threw Go’s new “testing/synctest” package at a particularly gnarly part of our codebase and were pleasantly surprised by how effective it was. This post covers the synctest package, its nuances, and how it does much more than speed up your tests. The main headline for Go 1.25’s synctest is its ability to magically advance time. Tests run in a “bubble” with a fake clock and calls to time.Sleep a
Introduction Playwright comes with three Playwright Test Agents out of the box: 🎭 planner, 🎭 generator and 🎭 healer. These agents can be used independently, sequentially, or as the chained calls in the agentic loop. Using them sequentially will produce test coverage for your product. 🎭 planner explores the app and produces a Markdown test plan 🎭 generator transforms the Markdown plan into th
Automated Unit Test Improvement using Large Language Models at Meta Nadia Alshahwan https://orcid.org/0009-0009-4763-0396 , Jubin Chheda https://orcid.org/0009-0005-0311-7890 , Anastasia Finegenova https://orcid.org/0009-0005-5824-5179 , Beliz Gokkaya https://orcid.org/0009-0003-0197-6806 , Mark Harman https://orcid.org/0000-0002-5864-4488 , Inna Harper https://orcid.org/0009-0008-9359-0949 , Alex
TL;DR Go 1.24 からは testing.B.Loop を使う 意図しない最適化を避けることができる N をループで使わないことで他の場所での使用を避けることができる ベンチマークの結果を比較する場合は同一条件下か確認しましょう ベンチマークの結果の安定性を確認しましょう 安定したベンチマークをするために testing.B.N は反復回数以外の用途で使わない 背景 なんでappendが速いんだろ🙄 pic.twitter.com/geEqBop2kv— ゴリラ - お餅で巻いたもち食感ロール(ショコラ)は良いぞ (@gorilla0513) 2025年2月19日 本題 まずは追試をします。 package main import "testing" func BenchmarkIndex(b *testing.B) { a := make([]int, b.N) b.Rese
Visual Studio Code supports running and debugging tests for your extension. These tests will run inside a special instance of VS Code named the Extension Development Host, and have full access to the VS Code API. We refer to these tests as integration tests, because they go beyond unit tests that can run without a VS Code instance. This documentation focuses on VS Code integration tests. Overview
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く