[{"data":1,"prerenderedAt":772},["ShallowReactive",2],{"blog-posts":3,"post-\u002Fblog\u002Fuser-acceptance-testing-in-software-development":177},[4,19,30,39,49,55,62,71,78,84,91,99,105,114,121,128,135,142,149,156,163,170],{"path":5,"title":6,"description":7,"date":8,"modified":9,"locale":10,"category":11,"image":12,"translationKey":18},"\u002Fblog\u002Fbest-website-feedback-tools","How to Choose a Website Feedback Tool (2026 Checklist)","How to choose the best website feedback tool in 2026: tool types, a 12-point checklist, a free scoring template and a one-week client trial plan.","2026-10-07T09:00:00+00:00","2026-10-08T09:00:00+00:00","en","guides",{"src":13,"card":14,"alt":15,"width":16,"height":17},"\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F09\u002Fscreencode_7_Bug_tracker_GiveFeedback-400x250.jpg","Code on a screen, illustrating how to choose a website feedback tool",1200,630,"feedback-tools",{"path":20,"title":21,"description":22,"date":8,"modified":8,"locale":10,"category":23,"image":24,"translationKey":29},"\u002Fblog\u002Fclient-website-approval","Client Website Approval: How to Get Sign-Off Without Delays","Client website approval made simple: the 5 approval stages, a revision-limit contract clause, a sign-off email template and a checklist you can reuse.","workflow",{"src":25,"card":26,"alt":27,"width":28,"height":16},"\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F06\u002FAutomating-Project-Management-for-Efficiency-Sized-400x250.jpg","Two people reviewing a printed document with a pen, ready for client website approval",1920,"client-approval",{"path":31,"title":32,"description":33,"date":8,"modified":8,"locale":10,"category":11,"image":34,"translationKey":38},"\u002Fblog\u002Fhow-to-collect-client-feedback-on-a-website","How to Collect Client Feedback on a Website (Step by Step)","How to collect client feedback on a website: compare 5 methods, run a clean review round step by step, and copy our sample briefing email for clients.",{"src":35,"card":36,"alt":37,"width":16,"height":17},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_web_Designer_GiveFeedback-400x250.jpg","Web designer at a desk reviewing client feedback on a website","client-feedback",{"path":40,"title":41,"description":42,"date":8,"modified":8,"locale":43,"category":11,"image":44,"translationKey":48},"\u002Fes\u002Fblog\u002Fanotar-capturas-de-pantalla-web","Cómo anotar capturas de pantalla de una web (y enviarlas)","Aprende a anotar capturas de pantalla de una web con Recortes, Markup, el navegador, apps dedicadas o un widget de feedback. Comparativa, precios y ejemplos.","es",{"src":45,"card":46,"alt":47,"width":16,"height":17},"\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F07\u002FFree_Bug_tracking_office_colours_pc_GiveFeedback-400x250.jpg","Persona en un ordenador anotando capturas de pantalla de una web para el desarrollador","screenshot-annotation",{"path":50,"title":51,"description":52,"date":8,"modified":8,"locale":43,"category":23,"image":53,"translationKey":29},"\u002Fes\u002Fblog\u002Faprobacion-cliente-proyecto-web","Aprobación del cliente en un proyecto web: cómo conseguirla","Aprobación del cliente en un proyecto web: las 5 fases, una cláusula para limitar revisiones, un email de aprobación listo para copiar y una checklist.",{"src":25,"card":26,"alt":54,"width":28,"height":16},"Dos personas revisan un documento con un bolígrafo antes de la aprobación del cliente en un proyecto web",{"path":56,"title":57,"description":58,"date":8,"modified":8,"locale":43,"category":23,"image":59,"translationKey":61},"\u002Fes\u002Fblog\u002Fcapturas-anotadas-en-asana","Capturas anotadas en Asana: cómo llevar el feedback web a tareas","Cómo llevar capturas anotadas y feedback web a Asana: adjuntos, Proofing, correo al proyecto, formularios o tareas automáticas desde un widget, comparados.",{"src":13,"card":14,"alt":60,"width":16,"height":17},"Capturas anotadas de una web convertidas en tareas de Asana","asana",{"path":63,"title":64,"description":65,"date":8,"modified":8,"locale":43,"category":11,"image":66,"translationKey":70},"\u002Fes\u002Fblog\u002Fchecklist-qa-web-antes-de-lanzar","Checklist web: más de 60 comprobaciones antes de lanzar","Checklist web con más de 60 comprobaciones por áreas: formularios, enlaces, móvil, navegadores, velocidad, SEO y accesibilidad, con plantilla Excel gratis.",{"src":67,"card":68,"alt":69,"width":16,"height":17},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracker_people_pc_GiveFeedback-400x250.jpg","Persona revisando una web con una checklist QA antes del lanzamiento","qa-checklist",{"path":72,"title":73,"description":74,"date":8,"modified":8,"locale":43,"category":11,"image":75,"translationKey":77},"\u002Fes\u002Fblog\u002Fcomo-escribir-un-informe-de-bugs","Plantilla de reporte de errores (bugs): gratis, con ejemplos","Plantilla de reporte de errores gratis en Excel y Word, con ejemplos de un informe de bugs bueno y uno malo, y los campos que importan en una web.",{"src":13,"card":14,"alt":76,"width":16,"height":17},"Código JavaScript en una pantalla, ilustrando cómo escribir un informe de bugs de una web","bug-report",{"path":79,"title":80,"description":81,"date":8,"modified":8,"locale":43,"category":11,"image":82,"translationKey":38},"\u002Fes\u002Fblog\u002Fcomo-recoger-feedback-de-clientes-en-una-web","Cómo pedir feedback a un cliente sobre su web (paso a paso)","Cómo recoger feedback de clientes en una web: 5 métodos comparados, un proceso de revisión paso a paso y un email de ejemplo para explicárselo al cliente.",{"src":35,"card":36,"alt":83,"width":16,"height":17},"Diseñador web en su mesa revisando el feedback de clientes sobre una web",{"path":85,"title":86,"description":87,"date":8,"modified":8,"locale":43,"category":23,"image":88,"translationKey":90},"\u002Fes\u002Fblog\u002Ffeedback-web-en-notion","Bugs en Notion: gestiona el feedback de tu web paso a paso","Cómo gestionar bugs en Notion en proyectos web: propiedades de la base de datos, vistas tablero y rutina de triaje, y cómo recibir el feedback del cliente solo.",{"src":25,"card":26,"alt":89,"width":28,"height":16},"Equipo organizando bugs y feedback de clientes de una web en Notion","notion",{"path":92,"title":93,"description":94,"date":8,"modified":8,"locale":43,"category":95,"image":96,"translationKey":98},"\u002Fes\u002Fblog\u002Fherramientas-gratis-seguimiento-bugs","Herramientas gratis de seguimiento de bugs para webs (2026)","Herramientas gratis de seguimiento de bugs para equipos web: GitHub Issues, Jira, Trello, Linear, Notion, Asana y feedback visual, con límites comprobados.","comparisons",{"src":67,"card":68,"alt":97,"width":16,"height":17},"Equipo revisando incidencias en una herramienta gratis de seguimiento de bugs","free-bug-tracking",{"path":100,"title":101,"description":102,"date":8,"modified":9,"locale":43,"category":11,"image":103,"translationKey":18},"\u002Fes\u002Fblog\u002Fmejores-herramientas-feedback-visual-web","Cómo elegir una herramienta de feedback visual para tu web","Cómo elegir entre las herramientas de feedback visual web en 2026: tipos, checklist de 12 criterios, plantilla de puntuación y prueba de una semana.",{"src":13,"card":14,"alt":104,"width":16,"height":17},"Código en una pantalla, ilustración de cómo elegir entre herramientas de feedback visual web",{"path":106,"title":107,"description":108,"date":8,"modified":8,"locale":43,"category":11,"image":109,"translationKey":113},"\u002Fes\u002Fblog\u002Fpruebas-de-aceptacion-uat-web","Pruebas de aceptación de usuario (UAT): ejemplos y plantilla","Qué son las pruebas de aceptación de usuario (UAT), diferencias con el QA, ejemplos de escenarios, criterios de aceptación y una plantilla gratis en Excel.",{"src":110,"card":111,"alt":112,"width":16,"height":17},"\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback.jpg","\u002Fwp-content\u002Fuploads\u002F2023\u002F08\u002FFree_Bug_tracking_testing-man_GiveFeedback-400x250.jpg","Cliente haciendo pruebas de aceptación UAT de su nueva web frente al ordenador","uat",{"path":115,"title":116,"description":117,"date":8,"modified":8,"locale":43,"category":11,"image":118,"translationKey":120},"\u002Fes\u002Fblog\u002Fque-es-el-feedback-visual","Qué es el feedback visual y por qué agiliza tus proyectos web","Qué es el feedback visual: comentarios sobre la propia web con capturas marcadas, vídeo o notas. Tipos, ventajas, ejemplos y qué pedirle a una herramienta.",{"src":35,"card":36,"alt":119,"width":16,"height":17},"Diseñador web revisando el feedback visual sobre una interfaz","visual-feedback",{"path":122,"title":123,"description":124,"date":125,"modified":8,"locale":10,"category":23,"image":126,"translationKey":90},"\u002Fblog\u002Fsupercharge-your-workflow-with-the-notion-bug-tracker-extension","Notion Bug Tracker Template (Free) for Website Projects","A free Notion bug tracker template for website projects: import the CSV, get the right properties and board views, and send client feedback into it.","2025-04-24T16:17:44+00:00",{"src":25,"card":26,"alt":127,"width":28,"height":16},"Team organizing website bugs and client feedback in a Notion bug tracker",{"path":129,"title":130,"description":131,"date":132,"modified":8,"locale":10,"category":11,"image":133,"translationKey":113},"\u002Fblog\u002Fuser-acceptance-testing-in-software-development","User Acceptance Testing (UAT): Template, Checklist & Examples","What user acceptance testing is, UAT vs QA, example test scenarios, exit criteria and a free UAT test plan and sign-off template (Excel) for websites.","2023-09-28T17:32:27+00:00",{"src":110,"card":111,"alt":134,"width":16,"height":17},"Client doing user acceptance testing on a new website at his desk",{"path":136,"title":137,"description":138,"date":139,"modified":8,"locale":10,"category":95,"image":140,"translationKey":98},"\u002Fblog\u002Fbug-tracking-tools-free","Free Bug Tracking Tools for Web Teams (2026 Guide)","Free bug tracking tools for web teams compared: GitHub Issues, Jira, Trello, Linear, Notion, Asana and visual feedback tools, with verified free-plan limits.","2023-09-21T16:56:47+00:00",{"src":67,"card":68,"alt":141,"width":16,"height":17},"Team at a computer reviewing issues in a free bug tracking tool",{"path":143,"title":144,"description":145,"date":146,"modified":8,"locale":10,"category":11,"image":147,"translationKey":77},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report","Bug Report Template (Free Excel & Word) + Examples","Free bug report template for Excel, Google Sheets and Word, with good and bad bug report examples and the fields that matter for website bugs.","2023-09-11T14:43:18+00:00",{"src":13,"card":14,"alt":148,"width":16,"height":17},"JavaScript code on a screen, illustrating how to write a bug report for a website",{"path":150,"title":151,"description":152,"date":153,"modified":8,"locale":10,"category":23,"image":154,"translationKey":61},"\u002Fblog\u002F1-way-to-get-annotated-screengrabs-into-asana","Asana Bug Tracking: Get Annotated Screenshots into Tasks","Get annotated screenshots and website feedback into Asana: attachments, Proofing, email-to-task, Forms or automatic tasks from a feedback widget, compared.","2023-09-11T11:56:04+00:00",{"src":13,"card":14,"alt":155,"width":16,"height":17},"Annotated screenshots of a website being turned into Asana tasks",{"path":157,"title":158,"description":159,"date":160,"modified":8,"locale":10,"category":11,"image":161,"translationKey":70},"\u002Fblog\u002Fspeed-up-qa-testing","Website QA Checklist: 60+ Checks Before Launch (Free Template)","A website QA checklist with 60+ checks grouped by area (forms, links, devices, browsers, speed, SEO, accessibility), plus a free Excel template to download.","2023-08-19T11:32:36+00:00",{"src":67,"card":68,"alt":162,"width":16,"height":17},"Person running a website QA checklist on a laptop before launch",{"path":164,"title":165,"description":166,"date":167,"modified":8,"locale":10,"category":11,"image":168,"translationKey":120},"\u002Fblog\u002Fvisual-feedback-faster-bug-testing","What Is Visual Feedback? A Guide for Web Teams","What is visual feedback? Feedback given on the website itself with marked-up screenshots, video or pinned comments. Types, benefits, examples, tool checklist.","2023-08-09T17:41:00+00:00",{"src":35,"card":36,"alt":169,"width":16,"height":17},"Web designer reviewing visual feedback on a website interface",{"path":171,"title":172,"description":173,"date":174,"modified":8,"locale":10,"category":11,"image":175,"translationKey":48},"\u002Fblog\u002Fscreen-grab-annotation-apps","How to Annotate Website Screenshots (and Send Them to Devs)","How to annotate website screenshots with OS tools, browser features, dedicated apps or a feedback widget. Compare options and prices, with a good example.","2023-08-02T23:25:13+00:00",{"src":45,"card":46,"alt":176,"width":16,"height":17},"Person at a computer annotating website screenshots for a developer",{"id":178,"title":130,"body":179,"category":11,"date":132,"description":131,"extension":742,"faq":743,"image":759,"locale":10,"meta":760,"modified":8,"navigation":761,"path":129,"seo":762,"seoTitle":763,"stem":764,"tags":765,"tldr":770,"translationKey":113,"__hash__":771},"blog\u002Fblog\u002Fuser-acceptance-testing-in-software-development.md",{"type":180,"value":181,"toc":730},"minimark",[182,186,192,197,205,208,211,215,267,270,274,277,360,369,373,414,418,421,555,558,562,565,568,607,610,619,622,629,637,640,644,647,672,675,680,683,687,719,727],[183,184,185],"p",{},"User acceptance testing (UAT) is the final round of testing in which the client or real users check that a website or web app does what they need before it goes live. On agency projects it's also the moment the client formally says \"yes, this is what we ordered\". This guide covers who does it, how it differs from QA, how to plan it with a test scenario template, how to collect issues and when to call it done.",[187,188],"template-download",{"files":189,"text":190,"title":191},"Excel|\u002Ftemplates\u002Fuat-test-plan-template.xlsx","Excel: test scenarios with pass\u002Ffail tracking, plus a sign-off sheet with acceptance criteria.","Free UAT test plan template",[193,194,196],"h2",{"id":195},"what-is-user-acceptance-testing","What is user acceptance testing?",[183,198,199,200,204],{},"User acceptance testing is testing done by the people who will own or use the product, against their real tasks, to decide whether they accept it. The developer asks \"does it work?\"; UAT asks \"does it work ",[201,202,203],"em",{},"for us","?\".",[183,206,207],{},"For a website, that means the client's marketing manager publishing a blog post in the CMS, the sales team receiving the contact form leads, or a customer buying a product with a discount code. For a web app, it's the users doing their daily job in the new system.",[183,209,210],{},"UAT normally ends with a sign-off: a written approval that the site can go live and the project phase is complete. That sign-off matters for the agency too, because it marks where the agreed scope ends and new requests begin.",[193,212,214],{"id":213},"who-does-uat","Who does UAT?",[216,217,218,231],"table",{},[219,220,221],"thead",{},[222,223,224,228],"tr",{},[225,226,227],"th",{},"Role",[225,229,230],{},"What they do in UAT",[232,233,234,243,251,259],"tbody",{},[222,235,236,240],{},[237,238,239],"td",{},"Client \u002F product owner",[237,241,242],{},"Runs the scenarios, decides what is a blocker, gives the final sign-off",[222,244,245,248],{},[237,246,247],{},"Client staff or end users",[237,249,250],{},"Test the tasks they'll do every day (editing content, handling orders)",[222,252,253,256],{},[237,254,255],{},"Project manager (agency)",[237,257,258],{},"Writes the scenarios with the client, sets dates, triages issues",[222,260,261,264],{},[237,262,263],{},"Developer \u002F designer",[237,265,266],{},"Prepares the staging site, fixes issues, doesn't test their own work here",[183,268,269],{},"The key rule: the people who built the site don't do the acceptance testing. They already know how it's supposed to work, so they don't see the problems a first-time user hits.",[193,271,273],{"id":272},"uat-vs-qa-whats-the-difference","UAT vs QA: what's the difference?",[183,275,276],{},"QA and UAT are often confused because both involve \"testing the site\". They answer different questions:",[216,278,279,292],{},[219,280,281],{},[222,282,283,286,289],{},[225,284,285],{},"Aspect",[225,287,288],{},"QA (quality assurance)",[225,290,291],{},"UAT (user acceptance testing)",[232,293,294,305,316,327,338,349],{},[222,295,296,299,302],{},[237,297,298],{},"Question",[237,300,301],{},"Is it built correctly?",[237,303,304],{},"Is it the right thing for us?",[222,306,307,310,313],{},[237,308,309],{},"Who",[237,311,312],{},"Agency or developer team",[237,314,315],{},"Client and\u002For real users",[222,317,318,321,324],{},[237,319,320],{},"When",[237,322,323],{},"During and after development",[237,325,326],{},"After QA, just before launch",[222,328,329,332,335],{},[237,330,331],{},"Based on",[237,333,334],{},"Specification, technical checklist",[237,336,337],{},"Business tasks and goals",[222,339,340,343,346],{},[237,341,342],{},"Finds",[237,344,345],{},"Broken links, layout bugs, errors",[237,347,348],{},"Wrong workflows, missing content, unclear steps",[222,350,351,354,357],{},[237,352,353],{},"Ends with",[237,355,356],{},"Issues fixed",[237,358,359],{},"Formal sign-off",[183,361,362,363,368],{},"Do QA first. If the client starts UAT on a site full of broken forms and layout bugs, they'll spend their time reporting things you should have caught, and lose trust in the process. Our ",[364,365,367],"a",{"href":366},"\u002Fblog\u002Fspeed-up-qa-testing\u002F","website QA checklist"," covers that step.",[193,370,372],{"id":371},"how-to-plan-uat-in-6-steps","How to plan UAT in 6 steps",[374,375,376,384,390,396,402,408],"ol",{},[377,378,379,383],"li",{},[380,381,382],"strong",{},"Agree the scope."," List what will be tested: page templates, forms, checkout, CMS tasks, integrations. Anything outside that list is not part of acceptance.",[377,385,386,389],{},[380,387,388],{},"Write test scenarios with the client."," Each scenario is a real task, written as steps with an expected result (see the template below). Ten to twenty scenarios cover most brochure sites and small shops.",[377,391,392,395],{},[380,393,394],{},"Prepare the environment."," A staging site with final content, real email delivery and test-mode payments. Give testers logins if needed.",[377,397,398,401],{},[380,399,400],{},"Set dates and testers."," Name who tests what and the deadline. \"Whenever you have time\" means UAT never ends.",[377,403,404,407],{},[380,405,406],{},"Explain how to report issues."," One issue per report, with a screenshot and what they expected. More on this below.",[377,409,410,413],{},[380,411,412],{},"Agree sign-off criteria before testing starts",", not after.",[193,415,417],{"id":416},"test-scenario-template-with-examples","Test scenario template (with examples)",[183,419,420],{},"A test scenario describes a task, the steps to do it and the expected result. Testers fill in the last two columns.",[216,422,423,445],{},[219,424,425],{},[222,426,427,430,433,436,439,442],{},[225,428,429],{},"ID",[225,431,432],{},"Scenario",[225,434,435],{},"Steps",[225,437,438],{},"Expected result",[225,440,441],{},"Pass \u002F Fail",[225,443,444],{},"Notes",[232,446,447,465,483,501,519,537],{},[222,448,449,452,455,458,461,463],{},[237,450,451],{},"UAT-01",[237,453,454],{},"Visitor sends a quote request",[237,456,457],{},"Home > \"Get a quote\" > fill form > Send",[237,459,460],{},"Thank-you message shown; email arrives at sales@ within 5 min",[237,462],{},[237,464],{},[222,466,467,470,473,476,479,481],{},[237,468,469],{},"UAT-02",[237,471,472],{},"Customer buys with a discount code",[237,474,475],{},"Shop > add 2 items > cart > apply code SPRING10 > pay (test card)",[237,477,478],{},"10% discount applied; order confirmation email sent",[237,480],{},[237,482],{},[222,484,485,488,491,494,497,499],{},[237,486,487],{},"UAT-03",[237,489,490],{},"Editor publishes a news post",[237,492,493],{},"Log in > Posts > Add new > add image > Publish",[237,495,496],{},"Post appears on \u002Fnews\u002F with image and correct date",[237,498],{},[237,500],{},[222,502,503,506,509,512,515,517],{},[237,504,505],{},"UAT-04",[237,507,508],{},"Mobile visitor finds opening hours",[237,510,511],{},"Open site on phone > menu > Contact",[237,513,514],{},"Hours visible without zooming; phone number is tappable",[237,516],{},[237,518],{},[222,520,521,524,527,530,533,535],{},[237,522,523],{},"UAT-05",[237,525,526],{},"Visitor switches language",[237,528,529],{},"Home > language selector > ES",[237,531,532],{},"Same page in Spanish; menu and footer translated",[237,534],{},[237,536],{},[222,538,539,542,545,548,551,553],{},[237,540,541],{},"UAT-06",[237,543,544],{},"Customer resets password",[237,546,547],{},"My account > \"Forgot password\" > email link",[237,549,550],{},"Reset email arrives; new password works",[237,552],{},[237,554],{},[183,556,557],{},"Write scenarios in the client's words, around their goals (\"a customer buys…\"), not around technical components (\"WooCommerce checkout\"). If the client can't describe the expected result, that's a requirement that was never agreed, and better to find it now.",[193,559,561],{"id":560},"how-clients-and-testers-should-report-issues","How clients and testers should report issues",[183,563,564],{},"This is where most UAT rounds slow down. Clients are not testers: they send emails like \"the form doesn't work on my phone\" with no page, no phone model and no screenshot. Each vague report costs a round of questions.",[183,566,567],{},"Give them a simple format. A good UAT issue report includes:",[569,570,571,577,586,591,596,601],"ul",{},[377,572,573,576],{},[380,574,575],{},"Scenario ID"," (e.g. UAT-02), so you know what they were doing",[377,578,579,582,583],{},[380,580,581],{},"What happened"," and ",[380,584,585],{},"what they expected",[377,587,588],{},[380,589,590],{},"Page URL",[377,592,593],{},[380,594,595],{},"Device, operating system and browser",[377,597,598],{},[380,599,600],{},"A screenshot with the problem marked",[377,602,603,606],{},[380,604,605],{},"Severity",": blocker (can't launch), major (must fix before launch), minor (can wait)",[183,608,609],{},"Example:",[611,612,613],"blockquote",{},[183,614,615,618],{},[380,616,617],{},"UAT-02 — Discount code not applied on mobile","\nOn iPhone (Safari), after entering SPRING10 in the cart, the message \"Code applied\" appears but the total doesn't change. Expected: 10% off. URL: staging.example.com\u002Fcart\u002F. Severity: blocker.",[183,620,621],{},"You can ask for that by email, but clients forget half the fields. A visual feedback tool fills them in for you. With GiveFeedback.io, you add a script to the staging site and a feedback button appears. The client clicks it, marks the problem on a screenshot of the page, writes a title and description, and the report arrives with the URL, screen resolution, operating system, browser and version already attached. Testers don't need an account.",[183,623,624],{},[625,626],"img",{"alt":627,"src":628},"A feedback report in GiveFeedback.io showing the screenshot and the tester's browser data","\u002Fwp-content\u002Fuploads\u002F2024\u002F01\u002Fbrowser-1920-1080-1-task-info.jpg",[183,630,631,632,636],{},"You can invite the client to the project so they see a read-only list of everything reported and its status (Open, Resolved, Archived), and send each report to ",[364,633,635],{"href":634},"\u002Fasana-bug-tracking-tool\u002F","Asana"," or Notion as a task. It doesn't record video or console logs, so for a bug in a complex web app the developer may still need to reproduce it themselves, but for most website UAT a marked-up screenshot plus browser data is enough.",[638,639],"blog-cta",{},[193,641,643],{"id":642},"sign-off-criteria-when-is-uat-done","Sign-off criteria: when is UAT done?",[183,645,646],{},"Agree these before testing starts and write them in the project document. Typical criteria for a website:",[569,648,649,652,663,666,669],{},[377,650,651],{},"All test scenarios have been run at least once",[377,653,654,655,658,659,662],{},"No open ",[380,656,657],{},"blocker"," or ",[380,660,661],{},"major"," issues",[377,664,665],{},"Minor issues are listed with an agreed fix date (they don't block launch)",[377,667,668],{},"Change requests are logged separately and quoted",[377,670,671],{},"The client confirms in writing (email or a signed form)",[183,673,674],{},"A simple sign-off email from the client is enough on most projects:",[611,676,677],{},[183,678,679],{},"We've completed acceptance testing of the new website on staging. All scenarios UAT-01 to UAT-15 pass. The three minor issues in the list will be fixed in the first week after launch. We approve the site for go-live on 14 November.",[183,681,682],{},"Without written criteria, UAT turns into an open-ended list of \"one more thing\". With them, you have a clear line: the site does what was agreed, it launches, and anything new is the next phase.",[193,684,686],{"id":685},"common-uat-mistakes","Common UAT mistakes",[569,688,689,695,701,707,713],{},[377,690,691,694],{},[380,692,693],{},"Starting UAT before QA is finished."," The client spends their time on bugs you should have caught.",[377,696,697,700],{},[380,698,699],{},"No scenarios, just \"have a look\"."," You get opinions on colors instead of checks on tasks.",[377,702,703,706],{},[380,704,705],{},"Feedback in five channels."," Email, WhatsApp, calls and comments on a PDF. Pick one channel and say so.",[377,708,709,712],{},[380,710,711],{},"Mixing bugs and new requests."," Label them separately from day one.",[377,714,715,718],{},[380,716,717],{},"No deadline."," Put UAT dates in the plan and in the contract.",[183,720,721,722,726],{},"For a deeper look at the approval step itself, see our guide to ",[364,723,725],{"href":724},"\u002Fblog\u002Fclient-website-approval\u002F","client website approval",".",[183,728,729],{},"Write ten to twenty scenarios with the client this week, agree what \"done\" means, and choose one place for issues. That alone turns UAT from the most stressful part of a project into a short, predictable checklist.",{"title":731,"searchDepth":732,"depth":732,"links":733},"",2,[734,735,736,737,738,739,740,741],{"id":195,"depth":732,"text":196},{"id":213,"depth":732,"text":214},{"id":272,"depth":732,"text":273},{"id":371,"depth":732,"text":372},{"id":416,"depth":732,"text":417},{"id":560,"depth":732,"text":561},{"id":642,"depth":732,"text":643},{"id":685,"depth":732,"text":686},"md",[744,747,750,753,756],{"question":745,"answer":746},"What is user acceptance testing in simple terms?","User acceptance testing is when the people who will use or own the website try it out on real tasks and confirm it does what they asked for. It's the last check before launch and ends with their sign-off.",{"question":748,"answer":749},"Who performs UAT on a website project?","The client, their staff or a few real end users. The agency or developer prepares the test scenarios and the staging site, but doesn't run the tests themselves.",{"question":751,"answer":752},"How long should UAT take?","For a typical agency website, plan one to two weeks: a few days for the client to test, time for fixes, and a short re-test. Fix the dates in the project plan so UAT doesn't drag on.",{"question":754,"answer":755},"What happens if the client finds new requirements during UAT?","Log them separately as change requests. UAT checks the agreed scope; new features are quoted and scheduled after launch or as a separate phase.",{"question":757,"answer":758},"What is the difference between UAT and beta testing?","UAT happens before launch on a staging site with the client or selected users and ends in formal approval. Beta testing usually happens with a wider group of real users on a live or near-live product to gather feedback, without a formal sign-off.",{"src":110,"card":111,"alt":134,"width":16,"height":17},{},true,{"title":130,"description":131},"User Acceptance Testing (UAT): Free Template & Examples","blog\u002Fuser-acceptance-testing-in-software-development",[766,767,768,769],"user acceptance testing","UAT","website testing","client sign-off","User acceptance testing (UAT) is the final round of testing in which the client or real users check that a website or web app does what they need before it goes live. You plan it as a short list of real tasks (test scenarios) with expected results, the client runs them on staging and reports issues with screenshots, and the project is signed off when agreed criteria are met, such as no open critical bugs.","3e-DkovkLfDtvqqKgl0SiBEq0EvWIlKNnzM5oUB7G94",1792593618625]