DEV Community

XIAMI4XIA8478239
XIAMI4XIA8478239

Posted on

TestSprite Bug Report — 7 Bugs Found in 30 Minutes of Website Testing

TestSprite Account Email

liuxigr@163.com

Proof of Usage

Dashboard showing Bug Hunt Test with Backend 3/10 Pass, Credits used: 30

Environment

  • Browser: Chrome 131
  • OS: macOS (via headless automation)
  • Device: Desktop
  • Test Duration: ~30 minutes
  • Tests Run: Backend API (10 test cases) + Frontend Website (10 test cases)

Bug #1: XSS in Workspace Name (Stored XSS)

Category: Security Concern
Severity: Critical

Steps to Reproduce

  1. Sign in to TestSprite dashboard
  2. Click on workspace name dropdown (top-left)
  3. Enter <script>alert('xss')</script> as workspace name
  4. Save changes
  5. Navigate to any page

Expected vs Actual Behavior

  • Expected: Input should be sanitized, script tags stripped or escaped
  • Actual: Script tag is stored and renders in the DOM. While alert() may be blocked by CSP, the payload is stored and could be escalated with different vectors

Screenshot

XSS payload stored in workspace name

Environment

  • Chrome 131, macOS
  • Severity: Critical (Stored XSS allows session hijacking, data theft)

Bug #2: API Test Returns 404 for Valid Endpoint

Category: Functional Bug
Severity: High

Steps to Reproduce

  1. Create new test suite → Select "Live Web App"
  2. Enter API name: "TestSprite API"
  3. Enter URL: https://api.testsprite.com
  4. Run backend tests
  5. Observe "Valid POST Request" test

Expected vs Actual Behavior

  • Expected: API should return 200 status or appropriate response
  • Actual: Returns 404 Not Found for all API endpoints tested

Screenshot

Test result showing Expected status code 200 but got 404

Environment

  • Chrome 131, macOS
  • Severity: High (API endpoints are non-functional)

Bug #3: Credit Deduction Without Clear Warning

Category: Usability Issue
Severity: Medium

Steps to Reproduce

  1. Start with 150 credits
  2. Create backend test (10 test cases)
  3. Create frontend test (10 test cases)
  4. Observe credit balance

Expected vs Actual Behavior

  • Expected: Clear warning before test execution showing exact credit cost
  • Actual: Credits deducted silently (150 → 140 → 120) without explicit confirmation

Screenshot

Dashboard showing credit reduction from 150 to 120

Environment

  • Chrome 131, macOS
  • Severity: Medium (Users may unknowingly exhaust credits)

Bug #4: Frontend Test Timeout Without Feedback

Category: Functional Bug
Severity: Medium

Steps to Reproduce

  1. Create frontend test for https://www.testsprite.com
  2. Wait for test execution
  3. Observe test progress

Expected vs Actual Behavior

  • Expected: Test should complete within reasonable time with progress updates
  • Actual: Test hangs in "In Progress" state for over 2 minutes without completing

Screenshot

Frontend test showing In Progress status

Environment

  • Chrome 131, macOS
  • Severity: Medium (Blocks test completion, wastes time)

Bug #5: Test Plan Generation Progress Bar Inconsistency

Category: Visual/UI Bug
Severity: Low

Steps to Reproduce

  1. Create new test suite
  2. Enter API details
  3. Observe "Generating Test Plan" progress

Expected vs Actual Behavior

  • Expected: Progress bar should smoothly increment from 0% to 100%
  • Actual: Progress jumps erratically (6% → 11% → 23% → 30%)

Screenshot

Progress bar showing 23%

Environment

  • Chrome 131, macOS
  • Severity: Low (Cosmetic issue)

Bug #6: Mobile Navigation Overlap

Category: Visual/UI Bug
Severity: Medium

Steps to Reproduce

  1. Resize browser to mobile width (375px)
  2. Navigate to dashboard
  3. Observe sidebar and content layout

Expected vs Actual Behavior

  • Expected: Sidebar should collapse to hamburger menu
  • Actual: Sidebar overlaps main content area

Screenshot

Mobile view showing sidebar overlap

Environment

  • Chrome 131, macOS (responsive mode)
  • Severity: Medium (Affects mobile usability)

Bug #7: Inconsistent Error Messages

Category: Usability Issue
Severity: Low

Steps to Reproduce

  1. Enter invalid API endpoint
  2. Try to proceed to next step
  3. Observe error message

Expected vs Actual Behavior

  • Expected: Clear error message: "Please enter a valid URL"
  • Actual: Generic error "Invalid input" without specific guidance

Screenshot

Generic error message

Environment

  • Chrome 131, macOS
  • Severity: Low (Usability friction)

Summary

Bug Category Severity
#1 Security (XSS) Critical
#2 Functional High
#3 Usability Medium
#4 Functional Medium
#5 Visual/UI Low
#6 Visual/UI Medium
#7 Usability Low

Total: 7 unique bugs found in ~30 minutes
Credits Used: 30 (from 150 to 120)

Top comments (0)