@Siddhant_K_code@github@GitHubEng Siddhant - thanks for confirming. my guess is someone is curating a bunch of fake accounts for nefarious use later. these accounts have 1 or 2 projects and they try to comment here and there to gain "cred". the ones in my screenshot all end with "26" do you see some pattern?
"If you can build a verification system and give proper direction, AI can produce a highly complex, highly sophisticated piece of software and it can continue to refine it until it just works."
I think the release of Bun 1.4 marks the end of programming as we know it. Anthropic and OpenAI developers live in the near future and if we pay attention, it's what's coming for the rest of us by next year: https://t.co/zD9ZDfhVAV
Spent quality time at @APIdaysGlobal India last week and it was extremely valuable, exchanging notes with industry-experts and fellow-builders. Thank you Mehdi Medjaoui and Naresh Jain for the invite. I actively sought out opinions from API enthusiasts ranging from fresh graduates to veterans and asked many questions. What are teams seeing on the ground? How is adoption of AI going within the enterprise SDLC? Are you releasing to production without reading every single line of code?
I also got asked a lot of questions. Does AI worry you? Won’t teams just create their own test-automation tools? I have certainly given a lot of thought to this question!
My answer is that I’ve seen many teams decide to build their own API testing tool instead of choosing something open-source or off-the-shelf. Things look great for a while, the developers get a pat on the back, maybe even promoted. But guess what, after a while people tend to move to other projects or leave the company. And then the tool stagnates and becomes technical debt. It drags down the team and becomes one of those things that people don’t want to touch or work on.
So yes, it is the same argument. You can vibe code a testing tool for your project, sure. But is that really the best use of your time? Are you sure you want to maintain this very important part of your pipeline?
I am very thankful to be here in this moment where LLMs can amplify your unique skills, knowledge and experience. I have been shipping open-source software since the days of SourceForge - before Git was even a thing. In my opinion, the gap between an average developer and a good one will widen with AI.
AI amplifies the good parts. It also magnifies the bad.
Teams that are not mature at requirements and verification will be hit hard when coding stops being the bottleneck. When code-review is no-longer humanly feasible, teams will have their hands full keeping up with the velocity expectations of a gen-AI world. There will be no time to think about building testing tools. The only option is to focus on the core-business. Leave the business of testing tools to the experts!
Here below is one slide from my talk. When you can’t review all the code, you have to rely on some visualization of what the LLM has done. I think we need to prepare ourselves for a future where you are looking at more dashboards and reports.
But you are still accountable, you can’t shrug off an incident in production with the excuse that “it was written by AI”. That is the human approval step, auditable as a Git commit.
1/ Lean APIOps & AI Testing 🛠️ Shruti Mehta (Allianz) shares how to keep Apigee lightweight, Marco Antonio Sanz (@apiquality_io) integrates AI into deployment cycles, and @ptrthomas (@getkarate ) reveals how to make AI-generated tests audit-ready.
Many such cases.
Team building events and offsites optimize solely for one specific personality type.
Rare is the leader who designs team events in ways that work for the multitude of personalities that exist on every team.
Karate 2.0.10 has been released. If you have been holding off on upgrading to v2, now is the time!
Check out the re-designed HTML report! Dark-mode, tag filtering and JSON syntax coloring!
Thanks to all the users already on v2 and who filed issues, we closed 25 of them in this release.
Code coverage tells you which lines ran.
It can't tell you which of your APIs are actually tested.
Introducing API Coverage from Karate Labs - measure coverage against the contract itself, across REST, gRPC, GraphQL & Kafka.
Your API keys belong on your laptop.
Karate Xplorer: free desktop API client.
Runs your Postman collections as-is: pm.test, environments, scripts, all natively.
LLM agent built in. Bring your own model.
Karate Xplorer - a free desktop API client with an LLM agent built in.
→ Zero cloud. Your keys stay local
→ Zero paywall on core features
→ Zero per-seat fees
→ Zero migration: drop in your Postman collections.