Loading feed…
Atlassian0 Hot0 comments9 min read
How we used Agentic Pipelines to turn test coverage into a daily habit
AI summary
Bitbucket Pipelines đã triển khai một AI agent được lập lịch chạy hàng ngày để viết unit test tập trung và tạo pull request nhỏ có thể review. Giải pháp này tự động phát hiện mã chưa được test và tạo test case phù hợp cho từng module riêng lẻ, tránh các test case quá lớn. Kết quả là tỷ lệ test coverage của team tăng từ 65% lên 92% trong vòng 3 tháng nhờ test được thực hiện đều đặn. Hệ thống hoạt động dựa trên kết hợp LLM với custom script để phân tích dependency và xác định các function cần test trước tiên. Bài viết đáng học ở chỗ cách phân tách quy trình test thành các bước nhỏ, tự động và dễ quản lý thay vì tạo test batch lớn gây quá tải cho reviewer.
AI summaries can be wrong. Read the original before relying on anything important.
Why read it: Bài viết này giúp bạn hiểu cách sử dụng AI agent trong Bitbucket Pipelines để tự động tạo bài kiểm thử unit tập trung và mở PR có thể xem xét, biến việc test coverage thành thói quen hàng ngày.
What do you remember?
Answer 3 short questions to earn reward points for this article. Only do it if you want the points.
up to +17 points
3 questions · under a minute · optional
Source: https://www.atlassian.com/blog/development/using-agentic-pipelines-to-turn-test-coverage-into-daily-habit. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
8 Sync ecosystem
One account, the whole ecosystem
Read the news here, practice coding, follow structured courses and train for IELTS on our sibling products — all connected through one 8 Sync account.
8syncdev.com
8syncdev.comThe ecosystem home: product overviews, blog and full pricing.
ExploreCourses
course.8syncdev.comLearn along a clear roadmap: videos, auto-graded quizzes, certificates and mentors who ship for a living.
View the roadmapCoding practice
coding.8syncdev.com1,000 DSA problems in Vietnamese, auto-graded across 7 languages — many FREE, right in your browser.
Practice for freeIELTS
ielts.8syncdev.comAI grading for all four IELTS skills with detailed rubric feedback.
Try it freeZUS — AI IDE
zus.8syncdev.comA 22 MB AI IDE for Vietnamese devs.
Download freemind0
mind0.8syncdev.comOrganizational memory for AI agents.
ExploreAcoLeads
home-acoleads.8syncdev.comAI that staffs your Fanpage and qualifies leads for you.
Try itRecommended for you
JetBrains15 Hot14 min
Building a RAG Pipeline for Semantic Code Search: A Developer Diary and Field Notes
Part 2: Storage, Search, and Agent Tooling In this blog series, we aim to share some of the lessons we learned over the past six months as we built and rolled out Air Context, a production-grade RA
Daily Dose of Data Science | Avi Chawla | Substack99 Hot7 min
Agent Framework vs. Agent Harness, clearly explained!
+ a technique for 23x faster attention!
AWS4 Hot2 min
Announcing Web Answer on Amazon Bedrock AgentCore
Discover more about what's new at AWS with Announcing Web Answer on Amazon Bedrock AgentCore
Awesome Java Newsletter2 Hot5 min
How to Automate Testing of a Java Swing Application
Java Swing testing for real installed apps, with plain-language steps instead of component names.
Sliver C2 Documentation2 Hot9 min
What Is an Agent Harness? How AI Security Tools Work
An AI agent harness manages how a model uses tools, context, and feedback. Learn how harness design shapes the reliability of AI security testing tools.
DEV2 Hot5 min
Don't Write Markdown Files for Your Coding Agent. Write Scripts.
If you want agents to do what you want, you need to learn how to box them into deterministic actions.... Tagged with ai, programming, devops, productivity.
ByteByteGo33 Hot14 min
How Netflix Uses AI Agents for Performance Engineering
The Netflix engineering team has developed an autonomous performance agent system. In this article, we’ll be learning more about it.
Zac Sweers1 Hot2 min
Stop Sending Tall PR Stacks
Stacked PRs are being overused and should stay the exception, not the norm, Zac Sweers argues. Small, logical commits reviewed commit by commit already make even large PRs reviewable, he says, criticizing GitHub for forcing reviews through an alphabetical files tab instead. Now that GitHub supports stacked PRs, he's seen stacks of 15 changes that must be merged serially, which multiply overhead, CI runs and code reviews by 15x. He suggests capping stack height around 5, and only for genuinely large changes.
Comments
Loading comments…