We are a UK-based B2B engineering company operating a structured marketing and e-commerce website. We are entering an optimisation phase and require a comprehensive Technical QA Audit focused on functional integrity, payment flow validation, and structured issue logging. This is not a marketing, SEO, or design review. We require technical QA testing with developer-ready outputs. Testing will occur on the live site within a defined window. Stripe test credentials will be provided. All test activity must be clearly labelled to avoid internal confusion. ⸻ Scope of Work The audit should cover the following areas: ⸻ 1️⃣ Core Functional Testing • Enquiry forms (validation, submission, success behaviour) • File upload behaviour (size/type limits, mobile upload) • Search and filtering functionality • Pagination and navigation behaviour • 404 handling and broken link identification • Mobile responsiveness and interaction behaviour • Form error messaging clarity • Back-button and refresh behaviour on key pages ⸻ 2️⃣ Payment & Quote Flow Validation (High Priority) • Full Stripe checkout testing (success and failure scenarios) • Card validation errors • Page refresh during payment • Session timeout behaviour • Back-button behaviour during checkout • Quote-based payment links (if applicable) • Confirmation page behaviour • Confirmation email triggers • Multiple payment attempt behaviour • Verification that duplicate charges cannot occur All payment testing must use Stripe test environment only. ⸻ 3️⃣ GA4 Event Integrity (Basic Validation) • Confirmation that key conversion events fire correctly • Verification that events fire once only • Refresh/back-button testing on success pages • Validation that Stripe redirect does not cause duplicate events Advanced attribution or UTM analysis is not required at this stage. ⸻ 4️⃣ Console & Front-End Stability • Identification of JavaScript console errors • Failed network requests • Broken assets or missing resources • UI breakage across key browsers ⸻ 5️⃣ Cross-Browser & Device Testing Minimum expected coverage: • Chrome (desktop) • Safari (desktop) • Edge (desktop) • iPhone Safari • Android Chrome (if available) Please confirm your device/browser capability. ⸻ 6️⃣ End-to-End Journey Testing Simulated real-user journey testing from: • Homepage → Category → Product → Enquiry • Quote received → Payment → Confirmation This ensures full commercial flow validation. ⸻ Deliverables We require: • Individual issues logged clearly (one issue per finding) • Steps to reproduce • Expected vs actual behaviour • Browser/device used • Screenshot or short screen recording • Severity rating (Critical / High / Medium / Low) • Output structured so issues can be raised directly as GitLab tickets We do not require a monolithic PDF report. A short summary highlighting all Critical and High severity issues is required. ⸻ Engagement Details • Initial engagement expected: 8–12 hours • Testing will occur on live site within agreed time window • Stripe test credentials will be provided • All test submissions must be clearly labelled (e.g. “QA TEST – [Date]”) This engagement forms Phase 1 of a structured optimisation programme. Strong performance may lead to ongoing periodic QA work. ⸻ Please Confirm in Proposal • Relevant QA testing experience • Tools typically used • Device/browser testing capability • Availability • Experience testing Stripe or similar payment flows Please begin your proposal with the word “Structured” so we know you have read the brief carefully. Thanks! Luke