Overview
Test summary generation is manual, fragmented, and error-prone. This workflow automates data gathering from internal FollowUp APIs and Jira, categorizes defects and progress, and uses AI to produce structured, standardized reports. It saves time, ensures consistency, and accelerates test retrospectives and release reviews.
The Impact
- Eliminate manual data wrangling. Automate pulling and organizing version, defect, and test progress data.
- Standardize reporting. Generate unified, project-compliant summaries with AI models.
- Accelerate retrospectives. Provide instant insights for test managers and release leads.
- Enable timely review. Auto-create Jira issues and notify stakeholders for prompt manual validation.
Who This Is For
- Test Managers who need batch automation of test summaries across multiple releases.
- Release Leads seeking quick defect and risk overviews to support go/no-go decisions.
- Product Owners wanting detailed, data-driven retrospectives for continuous improvement.
- R&D Teams aiming to archive structured release knowledge and track defect evolution.
How It Works
- Data Collection
- Query internal FollowUp APIs to fetch published KIDS version info and related test records.
- Defect & Progress Retrieval
- Pull Jira defect data filtered by version, including escaped and deferred defects, plus test submission and feedback records.
- Data Organization
- Extract key fields, categorize defects by status and version, and format data for analysis.
- AI-Powered Report Generation
- Feed structured data into large language models to generate detailed, professional test summary reports.
- Report Publication & Notification
- Create Jira issues with the summaries and send email alerts to assigned reviewers for manual verification.
What You'll Need
Before using this template, make sure you have:
- Authorized access to internal FollowUp APIs (GetPublishCards, GetTesterStepInfos, GetSubmitTestRecords, GetTestFeedbacks) with data fields like WorkId, PublishTime, InsertTime, DailyContent, FeedbackContent, JiraVersion.
- Jira project configured with required custom fields for test and release dates, affected/fix versions, defect details, status, and priority to enable accurate querying.
- Valid Jira credentials and Gmail/email sending credentials for report creation and notification.
- Knowledge of version naming conventions (e.g., Parental Android, Kids Android) to ensure correct filtering and mapping.
- Target email address for report delivery and optional WorkId or BeginTime for querying release records.
How to Use
- Step 1. Configure Credentials and Parameters
- Step 2. Run Data Collection
- Step 3. Analyze and Organize Data
- Step 4. Generate Test Summary Report
- Step 5. Verify Output and Notify
Set up Jira and email credentials; provide ReportEmail, and optionally WorkId or BeginTime for release data retrieval.
Trigger the workflow to fetch published version info and associated test and defect data automatically.
Let the workflow categorize defects, extract key progress points, and prepare data for reporting.
Use the integrated AI models to produce a professional, structured test summary based on collected data.
Confirm the Jira issue with the summary is created and email notification is sent for manual review and follow-up.
