Developer Builds Open-Source AI Agent That Reads Jira Tickets and Runs Browser Tests

·19 views

A developer has created an AI-powered QA agent that accepts a Jira ticket ID and a test environment URL, then autonomously reads the ticket, generates test steps, and executes them in a live Chrome browser window. The tool is built on two open-source components: Agent Factory, a studio for designing and managing agents, and BaaS (Browser as a Service), which handles actual browser interactions such as clicking, waiting, and taking screenshots. The setup requires a GitHub account, an OpenAI or Anthropic API key, Google Chrome, and optionally Docker and Go for local execution. Users configure the agent by cloning the Agent Factory repository, setting up BaaS locally or via Docker, and linking their Atlassian API credentials so the agent can access Jira ticket details. Once configured, the Test Orchestrator agent can be pointed at any test environment URL, enabling automated browser-based QA checks driven directly by Jira ticket content.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Build a 12-Seat Voice Room With WebRTC, Coin Economy, and Moderation

A technical breakdown outlines how to architect a multi-seat social voice room that handles real-time audio, virtual currency, and moderation without compromising performance or safety. For audio routing, the design recommends a Selective Forwarding Unit (SFU) over mesh or MCU topologies, as it limits upstream tracks to a maximum of 12 regardless of audience size. Seat management is treated like a multiplayer game state, with all changes processed server-side using atomic transactions and version-controlled broadcasts to prevent client-side manipulation. Virtual coin gifting is handled entirely on the server, which validates prices, checks balances, and writes immutable ledger entries within a single database transaction to prevent fraud. Moderation is built into the architecture itself, ensuring that revoking a seat also strips the user's SFU publish permission so kicked participants cannot continue speaking.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Shares Docker Basics: Installation, Dockerfiles, and Image Deployment

A developer documented foundational Docker exercises as part of a Kubernetes learning series, covering installation and verification using the hello-world container. The guide explains how to write a Dockerfile to build a Node.js application image using Alpine Linux as a lightweight base OS. Key Docker commands are demonstrated, including running containers in detached mode, port mapping, and managing container logs. The tutorial also walks through tagging a custom image and pushing it to Docker Hub under a personal account. Differences between docker ps and docker ps -a are highlighted to distinguish running containers from all containers including stopped ones.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Five-Pass Editing Method That Goes Beyond Proofreading to Fix Structure

A professional prose editor working in English and French has outlined a structured five-pass editing process designed to address deeper issues than simple typos. The method runs in a fixed sequence: checking paragraph-level argument structure, cutting redundant opening and closing sections, ensuring sentences name clear actors, replacing abstract language with specific details, and finally reading aloud. Each pass targets a single problem in isolation, as mixing them causes each to interfere with the others. The author argues that most writers already sense which parts of their work are weak but struggle to cut what cost them effort to write. According to the piece, running these passes in the correct order is what separates clean writing from writing that actually lands.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Beginner Developer Shares Journey Learning HTML, CSS, and JavaScript

A beginner web developer has shared their self-taught journey through the core technologies of front-end web development: HTML, CSS, and JavaScript. They started with HTML to learn webpage structure, then moved to CSS for styling and design, before tackling JavaScript to add interactivity and dynamic functionality. The learner noted that JavaScript posed the steepest challenge, requiring stronger logical thinking and problem-solving compared to the earlier tools. Despite facing bugs and frustrating setbacks, they credit each mistake as a learning opportunity that built patience and persistence. Looking ahead, they aim to develop a professional portfolio, build and publish complete websites, and continue advancing their skills through hands-on projects.

0 comments Read more at DEV Community