lorantest-judge-bug

Analyze test scripts and execution logs to categorize script issues and system bugs.

11|1|Updated Mar 31, 2023
One-click install
npx skills add https://github.com/WaterLoran/LoranTest --skill lorantest-judge-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lorantest-judge-bug
Source: https://github.com/WaterLoran/LoranTest/tree/main/.cursor/skills/lorantest-judge-bug
Command: npx skills add https://github.com/WaterLoran/LoranTest --skill lorantest-judge-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you systematically analyze test scripts and execution logs to identify and categorize both script quality issues and potential system bugs, streamlining the debugging process.

Core Features & Use Cases

  • Script Quality Review: Evaluate test scripts against defined quality standards, logging issues found.
  • Log Analysis: Locate and interpret execution logs to diagnose system behavior.
  • Bug Triage: Differentiate between script errors and actual system defects, categorizing them for reporting.
  • Use Case: After a test run fails, use this Skill to first check if the test script itself has quality issues (e.g., vague assertions, missing cleanup). If the script is sound, proceed to analyze the logs to pinpoint the exact system bug and record it with relevant details.

Quick Start

Analyze the test script located at '/path/to/your/test_script.py' and its corresponding logs to identify any issues.

Frequently Asked Questions about lorantest-judge-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze test scripts and execution logs to identify system bugs?

To analyze test scripts and execution logs for system bugs, you can review script adherence to quality standards, locate logs via file naming conventions, and diagnose defects based on request/response data and assertion failures.

What is the best way to differentiate between script quality issues and actual system defects during debugging?

Differentiating script issues from system defects involves evaluating test scripts against quality standards to catch vague assertions or missing cleanup, then analyzing execution logs to pinpoint actual system bugs if the script is sound.

Can I use this to review automation framework scripts for missing cleanup and vague assertions?

Yes, you can review automation framework test scripts against defined quality standards to identify and log issues like vague assertions and missing cleanup before proceeding to log analysis.

How do I locate relevant execution logs using file naming and path conventions for bug detection?

For bug detection, you locate relevant execution logs by following structured file naming and path conventions, then interpreting the request/response data and assertion failures within those logs to diagnose system behavior.

Does this process support creating issue reports for both script problems and confirmed system bugs?

Yes, the process supports creating structured issue reports that categorize and record details for both identified test script quality problems and confirmed system bugs diagnosed from execution logs.