Table of Contents
Back to Guides

Testing Guide - Phase 1

🧪 How to Test the PR Review Utility

Prerequisites

  • BitBucket account with at least one repository
  • At least one Pull Request in that repository
  • App Password configured

1️⃣ Configuration Test

Test BitBucket Credentials

File: appsettings.json

Steps:

  1. Open appsettings.json
  2. Verify all fields are filled: 
    {
  "BitBucket": {
    "BaseUrl": "https://api.bitbucket.org/2.0",
    "Workspace": "your-workspace",        // ✓ Check this
    "Username": "your-username",          // ✓ Check this
    "AppPassword": "ATBBxxx..."           // ✓ Check this
  }
}

Expected Result: No errors when starting the app

If it fails: Double-check your BitBucket Personal Settings

2️⃣ Application Startup Test

Test .NET Core Application

Steps:

cd PRReviewUtility
dotnet restore
dotnet build
dotnet run

Expected Output:

info: Microsoft.Hosting.Lifetime[0]
      Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://localhost:5000

If it fails:

  • Check .NET 5 SDK is installed: dotnet --version
  • Look for build errors in console
  • Verify all NuGet packages restored

3️⃣ UI Loading Test

Test Web Interface

Steps:

  1. Open browser
  2. Navigate to http://localhost:5000
  3. Check page loads

Expected Result:

  • ✅ Page displays "PR Review Utility" header
  • ✅ Form with Repository and PR ID fields visible
  • ✅ "Fetch Diff" button present
  • ✅ No console errors (F12 → Console)

Visual Checklist:

┌─────────────────────────────────┐
│ 🔹 PR Review Utility            │ ← Header visible?
├─────────────────────────────────┤
│ Repository: [________]          │ ← Input field?
│ PR ID:      [________]          │ ← Input field?
│             [Fetch Diff]        │ ← Button?
└─────────────────────────────────┘

4️⃣ API Endpoint Tests

Test REST API Directly

A. Get PR Details

curl http://localhost:5000/api/pr/YOUR-REPO/YOUR-PR-ID

Expected Response:

{
  "id": 42,
  "title": "Add new feature",
  "author": {
    "displayName": "John Doe"
  },
  "sourceBranch": "feature/new-feature",
  "destinationBranch": "main"
}

B. Get Diff

curl http://localhost:5000/api/pr/YOUR-REPO/YOUR-PR-ID/diff

Expected Response:

{
  "pullRequestId": 42,
  "repository": "YOUR-REPO",
  "filesChanged": 3,
  "files": [
    {
      "fileName": "Program.cs",
      "status": "modified",
      "additions": 10,
      "deletions": 5
    }
  ]
}

C. Get Raw Diff

curl http://localhost:5000/api/pr/YOUR-REPO/YOUR-PR-ID/diff/raw

Expected Response: Plain text unified diff

5️⃣ Full Workflow Test

Test Complete User Journey

Scenario: Review a pull request

Steps:

  1. Enter PR Details

    • Repository: my-test-repo
    • PR ID: 1
    • Click "Fetch Diff"

  2. Verify Loading State

    • ✅ Spinner appears
    • ✅ "Fetching pull request data..." message

  3. Check PR Details Section

    • ✅ Title displayed
    • ✅ Author name shown
    • ✅ Branch info correct
    • ✅ State badge visible (green/blue/red)
    • ✅ Files changed count accurate

  4. Check Files List

    • ✅ All changed files listed
    • ✅ Status badges (Added/Modified/Deleted)
    • ✅ +/- statistics per file
    • ✅ "View" button for each file

  5. View Individual File Diff

    • Click "View" on any file
    • ✅ Diff content expands
    • ✅ Code formatted properly
    • ✅ Can collapse again

  6. Test Raw Diff

    • Click "Toggle Raw Diff"
    • ✅ Raw diff section appears
    • ✅ Full unified diff visible
    • ✅ Can scroll through content

  7. Test Copy to Clipboard

    • Click "Copy to Clipboard" in raw diff
    • ✅ Button changes to "Copied!"
    • ✅ Paste in notepad to verify

  8. Test Export

    • Click "Export Diff as .txt"
    • ✅ File downloads
    • ✅ Filename: PR-{ID}-{REPO}-diff.txt
    • ✅ Open file - contains PR info + diff

6️⃣ Error Handling Tests

Test Error Scenarios

A. Invalid Repository

Steps:

  • Enter: Repository = fake-repo-xyz
  • Enter: PR ID = 1
  • Click "Fetch Diff"

Expected:

  • ✅ Red error alert appears
  • ✅ Message: "Failed to fetch pull request"
  • ✅ No crash, UI still responsive

B. Invalid PR ID

Steps:

  • Enter: Valid repository
  • Enter: PR ID = 999999
  • Click "Fetch Diff"

Expected:

  • ✅ Error alert with helpful message
  • ✅ Can try again with correct ID

C. Network Error

Steps:

  • Disconnect internet
  • Try to fetch PR

Expected:

  • ✅ Error message displayed
  • ✅ Application doesn't freeze

7️⃣ Browser Compatibility Test

Test Across Browsers

| Browser | Version | Test Status | |---------|---------|-------------| | Chrome | Latest | ✅ / ❌ | | Firefox | Latest | ✅ / ❌ | | Edge | Latest | ✅ / ❌ | | Safari | Latest | ✅ / ❌ |

What to Check:

  • Page layout renders correctly
  • Forms work properly
  • Buttons clickable
  • Diff displays with formatting
  • Export downloads file

8️⃣ Performance Tests

Test Large PRs

Scenario: PR with 50+ files

Steps:

  1. Find a large PR in your repository
  2. Fetch it through the UI
  3. Observe performance

Expected:

  • ✅ Loads within 5-10 seconds
  • ✅ File list renders completely
  • ✅ Can expand/collapse individual files
  • ✅ Export works without timeout

9️⃣ Edge Case Tests

A. Empty PR (No Changes)

Expected: Shows 0 files changed

B. PR with Binary Files

Expected: Binary files listed, no diff content

C. Deleted Files Only

Expected: Status shows "Deleted", deletions count shown

D. Very Long File Names

Expected: UI doesn't break, names wrap or truncate

🔟 Security Tests

Test Credential Security

Check:

  • ✅ App password not visible in browser
  • ✅ API calls don't expose credentials
  • ✅ appsettings.json in .gitignore
  • ✅ No credentials in JavaScript files

View Network Tab (F12 → Network):

  • Look at API requests
  • Verify Authorization header is not logged to console

✅ Acceptance Criteria

Phase 1 passes testing if:

Functional Requirements

  • [ ] Can configure BitBucket credentials
  • [ ] Application starts without errors
  • [ ] UI loads and displays correctly
  • [ ] Can fetch PR details successfully
  • [ ] Displays file list with statistics
  • [ ] Can view individual file diffs
  • [ ] Can view raw unified diff
  • [ ] Can copy diff to clipboard
  • [ ] Can export diff as .txt file
  • [ ] Error handling works properly

Non-Functional Requirements

  • [ ] Response time < 10 seconds for normal PRs
  • [ ] UI is responsive (works on mobile)
  • [ ] No JavaScript errors in console
  • [ ] Works on Chrome, Firefox, Edge
  • [ ] Code is clean and documented

🐛 Bug Report Template

If you find issues:

**Bug**: [Short description]

**Steps to Reproduce**:
1. 
2. 
3. 

**Expected Behavior**: 

**Actual Behavior**: 

**Environment**:
- OS: 
- Browser: 
- .NET Version: 

**Screenshots**: [if applicable]

**Console Errors**: [F12 → Console]

📊 Test Results Log

Document your testing:

Date: ___________
Tester: ___________

Test Cases:
[ ] Configuration Test - Pass / Fail
[ ] Application Startup - Pass / Fail
[ ] UI Loading - Pass / Fail
[ ] API Endpoints - Pass / Fail
[ ] Full Workflow - Pass / Fail
[ ] Error Handling - Pass / Fail
[ ] Browser Compatibility - Pass / Fail

Notes:
_________________________________
_________________________________

🎯 Next Steps After Testing

Once all tests pass:

  1. ✅ Document Issues: Note any bugs found
  2. ✅ Verify Fixes: Re-test after fixes
  3. ✅ Prepare for Phase 2: Ready for rule engine
  4. ✅ Deploy: Move to production if needed

💡 Testing Tips

  1. Start Simple: Test with a small, simple PR first
  2. Use Different Repos: Test with various repository types
  3. Test Edge Cases: Empty PRs, huge PRs, binary files
  4. Check Logs: Look at console output for warnings
  5. Save Test Data: Keep example PR IDs for future testing

Happy Testing! 🎉

Any issues? Check the README.md troubleshooting section.

Back to Guides