Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Writing tests is now the easiest part of your workflow. Pick a file, and Command Code will: - Analyze the code - Generate the right test cases - Run the test suite - Resolve failures - Re-run until all tests pass Try it on a file that hasn’t been... show more

Command Code

22,103 subscribers

20,517 görüntüleme • 1 ay önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

14 Yorum

Ahmad Awais profil fotoğrafı

Ahmad Awais29 gün önce

@MaedahBatool 🐐

fawn profil fotoğrafı

fawn1 ay önce

the goal is getting the test suite mad at me before production does

安叫兽|Bird🕊️ 🔶 BNB profil fotoğrafı

安叫兽|Bird🕊️ 🔶 BNB1 ay önce

听起来最难的是它真能把失败原因修对

Anra profil fotoğrafı

Anra1 ay önce

amasing news

Marly profil fotoğrafı

Marly29 gün önce

What’s the main benefit of ur harness?

RAZA | AI EXPLORER profil fotoğrafı

RAZA | AI EXPLORER28 gün önce

The easiest part of coding just got easier.

ènfer profil fotoğrafı

ènfer1 ay önce

When will qwen3.8 27b will. Be available?

mu profil fotoğrafı

mu1 ay önce

So does the Command Code plan actually support API calls? Can someone give me a definite answer?Can we use an API to call other agents?🧐

Alice The Ai Expert profil fotoğrafı

Alice The Ai Expert29 gün önce

Command Code turns testing from chore to one click win

ZenithAi profil fotoğrafı

ZenithAi26 gün önce

This makes reliable testing much more accessible for developers

Sani Ai Tech profil fotoğrafı

Sani Ai Tech28 gün önce

Automated test generation and fixing makes shipping much smoother

Aina Ai | Tools & Updates profil fotoğrafı

Aina Ai | Tools & Updates29 gün önce

Command Code turns testing from a chore into one click analyze generate run fix and ship

Elara AI profil fotoğrafı

Elara AI28 gün önce

This is the dream. Pick a file and it just... tests, debugs, fixes, and passes it for you No more staring at blank test files. Which untested file are you throwing at it first?

柳贯一 profil fotoğrafı

柳贯一28 gün önce

The usage page no longer shows cache hit tokens per call. This was essential for understanding cache efficiency and optimizing costs. Could you please bring it back? It’s hard to debug prompt caching without that visibility.

Benzer Videolar

Find and Fix Failing Tests Faster in VS Code Got a failing test in CI? See how VS Code’s Test Explorer makes it easy to filter your tests, find the failure, debug the issue, view test results, and rerun the test—all without leaving VS Code.

Find and Fix Failing Tests Faster in VS Code Got a failing test in CI? See how VS Code’s Test Explorer makes it easy to filter your tests, find the failure, debug the issue, view test results, and rerun the test—all without leaving VS Code.

Visual Studio Code

27,481 görüntüleme • 19 gün önce

claude code now writes its own test plan and runs it on a live iphone. i didn't write the tests. i didn't run the tests. i didn't even open the app. it caught the bug too.

claude code now writes its own test plan and runs it on a live iphone. i didn't write the tests. i didn't run the tests. i didn't even open the app. it caught the bug too.

Landseer Enga

30,714 görüntüleme • 4 ay önce

The first open-source implementation of the paper that will change automatic test generation is now available! In February, Meta published a paper introducing a tool to automatically increase test coverage, guaranteeing improvements over an existing code base. This is a big deal, but Meta didn't release the code. Fortunately, we now have Cover-Agent, an open-source tool you can install that implements Meta's paper to generate unit tests automatically: I recorded a quick video showing Cover-Agent in action. There are two things I want to mention: 1. Automatically generating unit tests is not new, but doing it right is difficult. If you ask ChatGPT to do it, you'll get duplicate, non-working, and meaningless tests that don't improve your code. Meta's solution only generates unique tests that run and increase code coverage. 2. People who write tests before writing the code (TDD) will find this less helpful. That's okay. Not everyone does TDD, but we all need to improve test coverage. There are many good and bad applications of AI, but this is one I'm looking forward to make part of my life.

The first open-source implementation of the paper that will change automatic test generation is now available! In February, Meta published a paper introducing a tool to automatically increase test coverage, guaranteeing improvements over an existing code base. This is a big deal, but Meta didn't release the code. Fortunately, we now have Cover-Agent, an open-source tool you can install that implements Meta's paper to generate unit tests automatically: I recorded a quick video showing Cover-Agent in action. There are two things I want to mention: 1. Automatically generating unit tests is not new, but doing it right is difficult. If you ask ChatGPT to do it, you'll get duplicate, non-working, and meaningless tests that don't improve your code. Meta's solution only generates unique tests that run and increase code coverage. 2. People who write tests before writing the code (TDD) will find this less helpful. That's okay. Not everyone does TDD, but we all need to improve test coverage. There are many good and bad applications of AI, but this is one I'm looking forward to make part of my life.

Santiago

774,662 görüntüleme • 2 yıl önce

New in v1.6.0 of the official Laravel VS Code Extension: Integration with VS Code's built-in test runner! Tests will now appear in the test explorer sidebar and you can run them right from the command palette. Works with both Pest and PHPUnit 👍 Shout out to Titas Gailius, knocked it outta the park 👏

New in v1.6.0 of the official Laravel VS Code Extension: Integration with VS Code's built-in test runner! Tests will now appear in the test explorer sidebar and you can run them right from the command palette. Works with both Pest and PHPUnit 👍 Shout out to Titas Gailius, knocked it outta the park 👏

Joe Tannenbaum

23,961 görüntüleme • 7 ay önce

i'm a little sick of chatgpt giving me obviously broken code i've found a "micro agent" approach to LLM code generation can work much better the LLM first generates a *test*, and then enters a loop where it generates and iterates on the code until the tests pass source below

i'm a little sick of chatgpt giving me obviously broken code i've found a "micro agent" approach to LLM code generation can work much better the LLM first generates a test, and then enters a loop where it generates and iterates on the code until the tests pass source below

Steve (Builder.io)

544,212 görüntüleme • 2 yıl önce

Alibaba just dropped an AI that doesn’t just write code. It runs it. Tests it. Fixes it. Until it actually works. Here’s what makes Qwen 3 Coder Next different: → Executes code, not just autocomplete → Runs tests automatically → Iterates until all tests pass → Handles multi-file repositories → Works fully offline This is a real coding agent, not a text generator. Save this video, you’ll rethink how coding gets done. Want the SOP? DM me. 💬

Alibaba just dropped an AI that doesn’t just write code. It runs it. Tests it. Fixes it. Until it actually works. Here’s what makes Qwen 3 Coder Next different: → Executes code, not just autocomplete → Runs tests automatically → Iterates until all tests pass → Handles multi-file repositories → Works fully offline This is a real coding agent, not a text generator. Save this video, you’ll rethink how coding gets done. Want the SOP? DM me. 💬

Julian Goldie SEO

20,956 görüntüleme • 7 ay önce

This is the dream of anyone who has ever tested a website. Writing automated tests for a UI is one of the hardest things ever. Here is how to write and run tests for your web pages 100x faster (it also supports iOS and Android apps).

This is the dream of anyone who has ever tested a website. Writing automated tests for a UI is one of the hardest things ever. Here is how to write and run tests for your web pages 100x faster (it also supports iOS and Android apps).

Santiago

31,529 görüntüleme • 1 ay önce

🤖 Debug Your Scripts in VS Code with GitHub Copilot Tired of remembering all the syntax for a launch.json file? In this quick tip, learn how to use GitHub Copilot to analyze your package.json, generate the right debug configurations, and launch your scripts directly with the built-in VS Code debugger.

🤖 Debug Your Scripts in VS Code with GitHub Copilot Tired of remembering all the syntax for a launch.json file? In this quick tip, learn how to use GitHub Copilot to analyze your package.json, generate the right debug configurations, and launch your scripts directly with the built-in VS Code debugger.

Visual Studio Code

40,335 görüntüleme • 23 gün önce

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

Santiago

140,922 görüntüleme • 9 ay önce

Flaky tests and memory leaks are the worst. Vitest now has a --detect-async-leaks flag that catches uncleared intervals, lingering servers, and other async operations leaking across your tests. ⚠️ Don't run it on every run though. Use it to audit your test suite, then clean things up. Available in the latest 4.1 beta. Big shout out to Ari from the Vitest team for landing this PR! 🔥

Flaky tests and memory leaks are the worst. Vitest now has a --detect-async-leaks flag that catches uncleared intervals, lingering servers, and other async operations leaking across your tests. ⚠️ Don't run it on every run though. Use it to audit your test suite, then clean things up. Available in the latest 4.1 beta. Big shout out to Ari from the Vitest team for landing this PR! 🔥

VoidZero

49,325 görüntüleme • 6 ay önce

President of Tanzania exposed the tests as fraudulent. He tested a goat, a bird, and a papaya fruit and all tested positive for “covid.” The “test” was used to fabricate cases to make it appear as if there was a pandemic.

President of Tanzania exposed the tests as fraudulent. He tested a goat, a bird, and a papaya fruit and all tested positive for “covid.” The “test” was used to fabricate cases to make it appear as if there was a pandemic.

Luiz M.D.

303,391 görüntüleme • 2 yıl önce

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Share Claude Code sessions with this command 👇 Just shipped v1.26.1 of claude-code-templates because I kept needing to hand off work mid-session. Run: npx claude-code-templates@latest --chats - All your sessions grouped by chat - Download any conversation To share a session: - Share the file, and add it to your project - Then run: claude "read @ chat-file .md and continue" Or if you are in the same account click on "Resume" and you will see the command: claude --resume session_id Built this to keep context flowing across the team without losing momentum.

Daniel San

10,787 görüntüleme • 10 ay önce

We've added a new command to Claude Code called /insights When you run it, Claude Code will read your message history from the past month. It'll summarize your projects, how you use Claude Code, and give suggestions on how to improve your workflow.

We've added a new command to Claude Code called /insights When you run it, Claude Code will read your message history from the past month. It'll summarize your projects, how you use Claude Code, and give suggestions on how to improve your workflow.

Thariq

1,236,896 görüntüleme • 7 ay önce

Terminal tip of the day: "Terminal: Run Recent Command..." surfaces history from the current session, previous session, and the common shell history file, providing similar functionality to a shell's reverse search.

Terminal tip of the day: "Terminal: Run Recent Command..." surfaces history from the current session, previous session, and the common shell history file, providing similar functionality to a shell's reverse search.

Visual Studio Code

29,213 görüntüleme • 1 yıl önce

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

Santiago

25,804 görüntüleme • 6 ay önce

CLAUDE CODE + SELF-CORRECTING LOOP = THE FASTEST WAY TO BUILD AND MONETIZE APPS most developers burn thousands of dollars manually debugging this setup forces Claude Opus 4.8 to self-correct - replacing a $95k/year QA engineer with a loop that costs $20/month: > Builder agent writes code while Checker agent runs tests (separating them eliminates blind spots) > Orchestrator loops them until all tests pass, capped at 5 runs to save tokens > Regression guard blocks loops if a fix breaks previously passing tests without loop guards, agents will literally edit your test suite to force a pass bookmark this guide to set up the exact loop commands 👇

CLAUDE CODE + SELF-CORRECTING LOOP = THE FASTEST WAY TO BUILD AND MONETIZE APPS most developers burn thousands of dollars manually debugging this setup forces Claude Opus 4.8 to self-correct - replacing a $95k/year QA engineer with a loop that costs $20/month: > Builder agent writes code while Checker agent runs tests (separating them eliminates blind spots) > Orchestrator loops them until all tests pass, capped at 5 runs to save tokens > Regression guard blocks loops if a fix breaks previously passing tests without loop guards, agents will literally edit your test suite to force a pass bookmark this guide to set up the exact loop commands 👇

Mr. Buzzoni

35,474 görüntüleme • 2 ay önce