09
Testing and defect tracking
Where I started: testing every document upload and API end to end, and turning failures into clear, reproducible Jira tickets.
- Role
- Full Stack Developer · Mavericks Tech Solutions
- When
- Sep 2025 – present
- Relevant for
- Testing & QASoftwareIT Support
01 Send a real document through the API in Postman.
My part
I owned QA on the platform: upload testing in Postman against the source documents, accuracy checked by hand across prompt and model changes, and user stories and defects in Jira.
Problem
An extraction platform can return a confident answer that is wrong. No tool can reliably check a scanned PDF, and the AI models themselves can hallucinate, so the final check has to be a person.
Approach
Upload real documents through the API in Postman and compare every extracted field with the scanned source. Log each mismatch in Jira with the file, the field, the expected value and steps to reproduce. Re-test after every prompt or model change to catch regressions.
Outcome
Defects anyone on the team could reproduce, and accuracy that was measured instead of assumed.
What I did
API upload testing
Real documents uploaded through the API in Postman.
PostmanREST APIs
Checked field by field
Every extracted field compared with the scanned source, by hand.
Reproducible defects
Each mismatch logged in Jira with the file, the field, the expected value and steps to reproduce.
Jira
Regression re-tests
The set rerun after every prompt or model change.
User stories
User stories written in Jira alongside the defects.
Stack
- Postman
- Jira
- REST APIs
- Python
- Log analysis