Sprint Board
What we're building.
Active and completed sprints — tickets organized by status to show what's in scope, in progress, and done.
fetching sprints…
Test Cases
How we decided to validate it.
Structured test cases that cover happy paths, edge cases and risk areas.
Bug Reports
What we found.
Clear, reproducible, actionable: steps, evidence, severity, priority and likely cause.
loading defects…
Automation
What we automated to protect it.
Cypress + TypeScript scripts written for real feature coverage, wired to CI.
CI · Cypress E2E
fetching runs…
API Testing
Live checks against real APIs.
Status codes, response shape and key field validation against the Jira and Cypress run status APIs powering this portfolio.
Live Environment
Not checked yetJira API—
Cypress Runs—
10 checks ready — press Run
| API | Endpoint | Method | Code | Time | Assertion | Result |
|---|---|---|---|---|---|---|
| JIRA | /api/jira-sprints | GET | — | — | Status 200 | — |
| JIRA | /api/jira-sprints | GET | — | — | `sprints` field present | — |
| JIRA | /api/jira-sprints | GET | — | — | At least 1 sprint returned | — |
| JIRA | /api/jira-sprints | GET | — | — | Sprint has `name` and `state` | — |
| JIRA | /api/jira-sprints | GET | — | — | Response time < 5000ms | — |
| CYPRESS | /api/cypress-status | GET | — | — | Status 200 | — |
| CYPRESS | /api/cypress-status | GET | — | — | `runs` field present | — |
| CYPRESS | /api/cypress-status | GET | — | — | Last run has `status` field | — |
| CYPRESS | /api/cypress-status | GET | — | — | Last run has `conclusion` | — |
| CYPRESS | /api/cypress-status | GET | — | — | Response time < 5000ms | — |
Analytics
These were the results.
Pass rates, bug resolution, automation coverage and CI run history.
loading analytics…