[{"data":1,"prerenderedAt":905},["ShallowReactive",2],{"blog-posts":3,"post-\u002Fblog\u002Fuser-acceptance-testing-in-software-development":281},[4,26,42,57,73,84,96,111,123,133,144,157,166,181,190,202,214,225,236,247,260,269],{"path":5,"title":6,"description":7,"date":8,"modified":9,"draft":10,"locale":11,"category":12,"image":13,"translationKey":19,"tags":20,"readingTime":25},"\u002Fblog\u002Fbest-website-feedback-tools","How to Choose a Website Feedback Tool (2026 Checklist)","How to choose the best website feedback tool in 2026: the tool types, 12 criteria, a free scoring template (Excel) and a one-week trial plan with a real client.","2026-10-07T09:00:00+00:00","2026-10-22T10:00:00+00:00",false,"en","guides",{"src":14,"card":15,"alt":16,"width":17,"height":18},"\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",[21,22,23,24],"best website feedback tool","website feedback tool free","visual website feedback tool","client feedback",8,{"path":27,"title":28,"description":29,"date":8,"modified":9,"draft":10,"locale":11,"category":30,"image":31,"translationKey":36,"tags":37,"readingTime":25},"\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 clause, a sign-off email, a free website sign-off form (Word) and a checklist.","workflow",{"src":32,"card":33,"alt":34,"width":35,"height":17},"\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",[38,39,40,41],"client approval process","website sign off","revision rounds","web agency",{"path":43,"title":44,"description":45,"date":8,"modified":9,"draft":10,"locale":11,"category":12,"image":46,"translationKey":50,"tags":51,"readingTime":56},"\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: 5 methods compared, a review round step by step, good vs vague feedback examples and a briefing email to send today.",{"src":47,"card":48,"alt":49,"width":17,"height":18},"\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",[52,53,54,55],"client feedback on website","website feedback examples","client feedback examples","website review process",9,{"path":58,"title":59,"description":60,"date":8,"modified":9,"draft":10,"locale":61,"category":12,"image":62,"translationKey":66,"tags":67,"readingTime":72},"\u002Fes\u002Fblog\u002Fanotar-capturas-de-pantalla-web","Cómo anotar capturas de pantalla de una web (Mac, Windows y online)","Cómo anotar capturas de pantalla en Windows, Mac, online o en Chrome, cómo capturar una página web entera y cómo marcar los errores para que se arreglen.","es",{"src":63,"card":64,"alt":65,"width":17,"height":18},"\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 anotando capturas de pantalla de una web para enviarlas al equipo de desarrollo","screenshot-annotation",[68,69,70,71],"anotar capturas de pantalla","captura de pantalla","anotar captura en Mac","anotar captura en Windows",7,{"path":74,"title":75,"description":76,"date":8,"modified":9,"draft":10,"locale":61,"category":30,"image":77,"translationKey":36,"tags":79,"readingTime":25},"\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, un formulario de aprobación gratis y una checklist.",{"src":32,"card":33,"alt":78,"width":35,"height":17},"Dos personas revisan un documento con un bolígrafo antes de la aprobación del cliente en un proyecto web",[80,81,82,83],"aprobación del cliente","rondas de revisión","presupuesto web","agencia web",{"path":85,"title":86,"description":87,"date":8,"modified":9,"draft":10,"locale":61,"category":30,"image":88,"translationKey":90,"tags":91,"readingTime":56},"\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: plantilla CSV gratis, cinco métodos comparados y tareas automáticas desde el feedback del cliente.",{"src":14,"card":15,"alt":89,"width":17,"height":18},"Capturas anotadas de una web convertidas en tareas de Asana","asana",[92,93,94,95],"capturas anotadas en Asana","plantilla Asana","gestión de bugs","feedback web",{"path":97,"title":98,"description":99,"date":8,"modified":9,"draft":10,"locale":61,"category":12,"image":100,"translationKey":104,"tags":105,"readingTime":110},"\u002Fes\u002Fblog\u002Fchecklist-qa-web-antes-de-lanzar","Checklist web: más de 70 comprobaciones antes de lanzar","Checklist web con más de 70 comprobaciones por áreas: formularios, enlaces, móvil, navegadores, velocidad, SEO, accesibilidad y WordPress, con plantilla Excel gratis.",{"src":101,"card":102,"alt":103,"width":17,"height":18},"\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",[106,107,108,109],"checklist web","checklist QA web","pruebas web","lanzamiento web",12,{"path":112,"title":113,"description":114,"date":8,"modified":9,"draft":10,"locale":61,"category":12,"image":115,"translationKey":117,"tags":118,"readingTime":56},"\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, Google Sheets y Word, con un ejemplo de informe de bugs bueno y uno malo y los campos que importan en una web.",{"src":14,"card":15,"alt":116,"width":17,"height":18},"Código JavaScript en una pantalla, ilustrando cómo escribir un informe de bugs de una web","bug-report",[119,120,121,122],"plantilla de reporte de errores","reporte de errores","informe de bugs","ejemplo de reporte de errores",{"path":124,"title":125,"description":126,"date":8,"modified":9,"draft":10,"locale":61,"category":12,"image":127,"translationKey":50,"tags":129,"readingTime":56},"\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 pedir feedback a un cliente sobre su web: 5 métodos comparados, una ronda de revisión paso a paso, ejemplos de feedback bueno y vago y un email para enviar hoy.",{"src":47,"card":48,"alt":128,"width":17,"height":18},"Diseñador web en su mesa revisando el feedback de clientes sobre una web",[130,131,95,132],"cómo pedir feedback a un cliente","feedback de clientes","revisión de una web",{"path":134,"title":135,"description":136,"date":8,"modified":9,"draft":10,"locale":61,"category":30,"image":137,"translationKey":139,"tags":140,"readingTime":25},"\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: plantilla gratis, propiedades, vistas tablero, rutina de triaje y cómo recibir el feedback del cliente solo.",{"src":32,"card":33,"alt":138,"width":35,"height":17},"Equipo organizando bugs y feedback de clientes de una web en Notion","notion",[141,142,143,95],"bugs en Notion","plantilla Notion","seguimiento de bugs",{"path":145,"title":146,"description":147,"date":8,"modified":9,"draft":10,"locale":61,"category":148,"image":149,"translationKey":151,"tags":152,"readingTime":56},"\u002Fes\u002Fblog\u002Fherramientas-gratis-seguimiento-bugs","Herramientas gratis de seguimiento de bugs para webs (2026)","Herramientas gratis de seguimiento de bugs para equipos web: los planes gratuitos de Jira, Trello, ClickUp, Notion, Asana, monday.com y Wrike, y una hoja de cálculo gratis.","comparisons",{"src":101,"card":102,"alt":150,"width":17,"height":18},"Equipo revisando incidencias en una herramienta gratis de seguimiento de bugs","free-bug-tracking",[153,154,155,156],"herramientas gratis seguimiento de bugs","bug tracker","gestión de incidencias","hoja de seguimiento de bugs",{"path":158,"title":159,"description":160,"date":8,"modified":9,"draft":10,"locale":61,"category":12,"image":161,"translationKey":19,"tags":163,"readingTime":56},"\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, 12 criterios, una plantilla de evaluación gratis en Excel y una prueba de una semana.",{"src":14,"card":15,"alt":162,"width":17,"height":18},"Código en una pantalla, ilustración de cómo elegir entre herramientas de feedback visual web",[164,95,165,131],"herramientas de feedback visual","feedback visual",{"path":167,"title":168,"description":169,"date":8,"modified":9,"draft":10,"locale":61,"category":12,"image":170,"translationKey":174,"tags":175,"readingTime":180},"\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, checklist para webs y plantillas gratis en Excel y Word.",{"src":171,"card":172,"alt":173,"width":17,"height":18},"\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",[176,177,178,179],"pruebas de aceptación","pruebas de aceptación de usuario","plan de pruebas de aceptación","ejemplo pruebas de aceptación",10,{"path":182,"title":183,"description":184,"date":8,"modified":9,"draft":10,"locale":61,"category":12,"image":185,"translationKey":187,"tags":188,"readingTime":25},"\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":47,"card":48,"alt":186,"width":17,"height":18},"Diseñador web revisando el feedback visual sobre una interfaz","visual-feedback",[165,95,189,131],"capturas anotadas",{"path":191,"title":192,"description":193,"date":194,"modified":9,"draft":10,"locale":11,"category":30,"image":195,"translationKey":139,"tags":197,"readingTime":25},"\u002Fblog\u002Fsupercharge-your-workflow-with-the-notion-bug-tracker-extension","Notion Bug Tracker Template (Free) for Website Projects","Free Notion bug tracker template for website projects: import the CSV, set up the properties and board views, and send client feedback into Notion.","2025-04-24T16:17:44+00:00",{"src":32,"card":33,"alt":196,"width":35,"height":17},"Team organizing website bugs and client feedback in a Notion bug tracker",[198,199,200,201],"notion bug tracker template","notion issue tracker template","bug tracking","website feedback",{"path":203,"title":204,"description":205,"date":206,"modified":9,"draft":10,"locale":11,"category":12,"image":207,"translationKey":174,"tags":209,"readingTime":56},"\u002Fblog\u002Fuser-acceptance-testing-in-software-development","User Acceptance Testing (UAT): Template, Checklist & Examples","What user acceptance testing is, UAT vs QA, test scenario examples, a UAT checklist for websites and free templates: Excel test plan and Word sign-off form.","2023-09-28T17:32:27+00:00",{"src":171,"card":172,"alt":208,"width":17,"height":18},"Client doing user acceptance testing on a new website at his desk",[210,211,212,213],"user acceptance testing","UAT testing","user acceptance testing template","user acceptance testing checklist for website",{"path":215,"title":216,"description":217,"date":218,"modified":9,"draft":10,"locale":11,"category":148,"image":219,"translationKey":151,"tags":221,"readingTime":56},"\u002Fblog\u002Fbug-tracking-tools-free","Free Bug Tracking Tools for Web Teams (2026 Comparison)","Free bug tracking tools compared for web teams: the free plans of Jira, Trello, ClickUp, Notion, Asana, monday.com and Wrike, plus a free bug tracking spreadsheet.","2023-09-21T16:56:47+00:00",{"src":101,"card":102,"alt":220,"width":17,"height":18},"Team at a computer reviewing issues in a free bug tracking tool",[222,154,223,224],"free bug tracking tools","bug tracking spreadsheet","issue tracking",{"path":226,"title":227,"description":228,"date":229,"modified":9,"draft":10,"locale":11,"category":12,"image":230,"translationKey":117,"tags":232,"readingTime":25},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report","Bug Report Template (Free Excel, Word & Google Sheets) + Examples","Free bug report template for Excel, Google Sheets and Word, with a good and a bad bug report example and the fields that matter for website bugs.","2023-09-11T14:43:18+00:00",{"src":14,"card":15,"alt":231,"width":17,"height":18},"JavaScript code on a screen, illustrating how to write a bug report for a website",[233,234,235,223],"bug report template","bug report example","how to write a bug report",{"path":237,"title":238,"description":239,"date":240,"modified":9,"draft":10,"locale":11,"category":30,"image":241,"translationKey":90,"tags":243,"readingTime":25},"\u002Fblog\u002F1-way-to-get-annotated-screengrabs-into-asana","Asana Bug Tracking: Free Template and Annotated Screenshots","Asana bug tracking for website projects: a free CSV template, five ways to get annotated screenshots into tasks, and automatic tasks from client feedback.","2023-09-11T11:56:04+00:00",{"src":14,"card":15,"alt":242,"width":17,"height":18},"Annotated screenshots of a website being turned into Asana tasks",[244,245,246,201],"asana bug tracking","asana bug tracking template","annotated screenshots",{"path":248,"title":249,"description":250,"date":251,"modified":9,"draft":10,"locale":11,"category":12,"image":252,"translationKey":104,"tags":254,"readingTime":259},"\u002Fblog\u002Fspeed-up-qa-testing","Website QA Checklist: 70+ Checks Before Launch (Free Template)","A website QA checklist with 70+ checks by area (forms, links, devices, browsers, speed, SEO, accessibility, WordPress), plus a free Excel and Google Sheets template.","2023-08-19T11:32:36+00:00",{"src":101,"card":102,"alt":253,"width":17,"height":18},"Person running a website QA checklist on a laptop before launch",[255,256,257,258],"website QA checklist","website testing checklist","website qa checklist template excel","wordpress website testing checklist",11,{"path":261,"title":262,"description":263,"date":264,"modified":9,"draft":10,"locale":11,"category":12,"image":265,"translationKey":187,"tags":267,"readingTime":25},"\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, examples and a tool checklist.","2023-08-09T17:41:00+00:00",{"src":47,"card":48,"alt":266,"width":17,"height":18},"Web designer reviewing visual feedback on a website interface",[268,23,246,201],"visual feedback",{"path":270,"title":271,"description":272,"date":273,"modified":9,"draft":10,"locale":11,"category":12,"image":274,"translationKey":66,"tags":276,"readingTime":72},"\u002Fblog\u002Fscreen-grab-annotation-apps","How to Annotate a Screenshot of a Website (Mac, Windows & Online)","How to annotate a screenshot on Mac, Windows, online or in Chrome, how to capture a full web page, and how to mark up website screenshots so developers fix them.","2023-08-02T23:25:13+00:00",{"src":63,"card":64,"alt":275,"width":17,"height":18},"Person at a computer annotating website screenshots for a developer",[277,278,279,280],"annotate screenshot","annotate screenshot mac","annotate screenshot windows","annotate screenshot online",{"id":282,"title":204,"body":283,"category":12,"date":206,"description":205,"draft":10,"extension":881,"faq":882,"image":897,"locale":11,"meta":898,"modified":9,"navigation":669,"path":203,"readingTime":56,"seo":899,"seoTitle":900,"stem":901,"tags":902,"tldr":903,"translationKey":174,"__hash__":904},"blog\u002Fblog\u002Fuser-acceptance-testing-in-software-development.md",{"type":284,"value":285,"toc":869},"minimark",[286,290,296,301,312,315,318,322,325,377,380,384,387,470,477,481,484,506,510,513,647,650,654,657,726,730,733,736,747,759,766,779,782,786,789,792,825,828,834,842,846,849,866],[287,288,289],"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\". When the client tests from written scenarios and the sign-off criteria are agreed before anyone starts, it ends with a clear yes instead of a trickle of new requests. The free test plan and sign-off form below are built for that.",[291,292],"template-download",{"files":293,"text":294,"title":295},"Excel|\u002Ftemplates\u002Fuat-test-plan-template.xlsx,Word|\u002Ftemplates\u002Fwebsite-sign-off-form.docx","Excel test plan with scenarios, pass\u002Ffail tracking and a sign-off sheet (opens in Google Sheets: File > Import), and a Word sign-off form for the client.","Free UAT templates",[297,298,300],"h2",{"id":299},"what-is-user-acceptance-testing-uat","What is user acceptance testing (UAT)?",[287,302,303,304,311],{},"User acceptance testing is testing done by the people who will own or use a product, against their real tasks, to decide whether they accept it. The developer asks \"does it work?\"; UAT asks \"does it work for us?\". The ",[305,306,310],"a",{"href":307,"rel":308},"https:\u002F\u002Fglossary.istqb.org\u002Fen_US\u002Fterm\u002Facceptance-testing",[309],"nofollow","ISTQB glossary",", the reference vocabulary for software testing, defines acceptance testing the same way: deciding whether a system satisfies the needs of its users.",[287,313,314],{},"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.",[287,316,317],{},"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.",[297,319,321],{"id":320},"who-performs-uat-on-a-website-project","Who performs UAT on a website project?",[287,323,324],{},"The client, their staff or a small group of real end users perform UAT; the agency prepares it and fixes what it finds. The client or product owner runs the scenarios, decides what blocks the launch and signs off; the project manager writes the scenarios with the client and triages issues; developers and designers fix them but don't test their own work here.",[326,327,328,341],"table",{},[329,330,331],"thead",{},[332,333,334,338],"tr",{},[335,336,337],"th",{},"Role",[335,339,340],{},"What they do in UAT",[342,343,344,353,361,369],"tbody",{},[332,345,346,350],{},[347,348,349],"td",{},"Client or product owner",[347,351,352],{},"Runs the scenarios, decides what is a blocker, gives the final sign-off",[332,354,355,358],{},[347,356,357],{},"Client staff or end users",[347,359,360],{},"Test the tasks they'll do every day (editing content, handling orders)",[332,362,363,366],{},[347,364,365],{},"Project manager (agency)",[347,367,368],{},"Writes the scenarios with the client, sets dates, triages issues",[332,370,371,374],{},[347,372,373],{},"Developer or designer",[347,375,376],{},"Prepares the staging site and fixes issues; doesn't test their own work here",[287,378,379],{},"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.",[297,381,383],{"id":382},"what-is-the-difference-between-uat-and-qa","What is the difference between UAT and QA?",[287,385,386],{},"QA asks whether the site is built correctly, and the team that builds it runs it against the specification during and after development. UAT asks whether it's the right thing for the client, and the client or real users run it against business tasks just before launch. QA ends with issues fixed; UAT ends with a formal sign-off.",[326,388,389,402],{},[329,390,391],{},[332,392,393,396,399],{},[335,394,395],{},"Aspect",[335,397,398],{},"QA (quality assurance)",[335,400,401],{},"UAT (user acceptance testing)",[342,403,404,415,426,437,448,459],{},[332,405,406,409,412],{},[347,407,408],{},"Question",[347,410,411],{},"Is it built correctly?",[347,413,414],{},"Is it the right thing for us?",[332,416,417,420,423],{},[347,418,419],{},"Who",[347,421,422],{},"Agency or developer team",[347,424,425],{},"Client and real users",[332,427,428,431,434],{},[347,429,430],{},"When",[347,432,433],{},"During and after development",[347,435,436],{},"After QA, just before launch",[332,438,439,442,445],{},[347,440,441],{},"Based on",[347,443,444],{},"Specification, technical checklist",[347,446,447],{},"Business tasks and goals",[332,449,450,453,456],{},[347,451,452],{},"Finds",[347,454,455],{},"Broken links, layout bugs, errors",[347,457,458],{},"Wrong workflows, missing content, unclear steps",[332,460,461,464,467],{},[347,462,463],{},"Ends with",[347,465,466],{},"Issues fixed",[347,468,469],{},"Formal sign-off",[287,471,472,473,476],{},"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 ",[305,474,255],{"href":475},"\u002Fblog\u002Fspeed-up-qa-testing\u002F"," covers that step.",[297,478,480],{"id":479},"how-do-you-plan-user-acceptance-testing","How do you plan user acceptance testing?",[287,482,483],{},"Plan UAT in six steps: agree what is in scope, write ten to twenty test scenarios with the client, prepare a staging site with final content and real email delivery, name who tests what and by when, explain how to report issues, and agree the sign-off criteria before anyone starts testing. Skipping the last step is what turns UAT into an endless list of extras.",[485,486,487,491,494,497,500,503],"ol",{},[488,489,490],"li",{},"Agree the scope: list what will be tested, such as page templates, forms, checkout, CMS tasks and integrations. Anything outside that list is not part of acceptance.",[488,492,493],{},"Write test scenarios with the client: each scenario is a real task, written as steps with an expected result (see the examples below). Ten to twenty cover most brochure sites and small shops.",[488,495,496],{},"Prepare the environment: a staging site with final content, real email delivery and test-mode payments, plus logins for the testers who need them.",[488,498,499],{},"Set dates and testers: name who tests what and the deadline. \"Whenever you have time\" means UAT never ends.",[488,501,502],{},"Explain how to report issues: one issue per report, with a screenshot and what they expected.",[488,504,505],{},"Agree sign-off criteria first: before testing starts, not after.",[297,507,509],{"id":508},"what-does-a-uat-test-scenario-look-like","What does a UAT test scenario look like?",[287,511,512],{},"It's a real task written as a short sequence of steps with an expected result, so the tester can mark it as passed or failed. It's phrased in the client's words around a business goal, such as \"a customer buys with a discount code\", rather than around a technical component. The tester fills in the result and any notes.",[326,514,515,537],{},[329,516,517],{},[332,518,519,522,525,528,531,534],{},[335,520,521],{},"ID",[335,523,524],{},"Scenario",[335,526,527],{},"Steps",[335,529,530],{},"Expected result",[335,532,533],{},"Pass \u002F Fail",[335,535,536],{},"Notes",[342,538,539,557,575,593,611,629],{},[332,540,541,544,547,550,553,555],{},[347,542,543],{},"UAT-01",[347,545,546],{},"Visitor sends a quote request",[347,548,549],{},"Home > \"Get a quote\" > fill form > Send",[347,551,552],{},"Thank-you message shown; email arrives at sales@ within 5 min",[347,554],{},[347,556],{},[332,558,559,562,565,568,571,573],{},[347,560,561],{},"UAT-02",[347,563,564],{},"Customer buys with a discount code",[347,566,567],{},"Shop > add 2 items > cart > apply code SPRING10 > pay (test card)",[347,569,570],{},"10% discount applied; order confirmation email sent",[347,572],{},[347,574],{},[332,576,577,580,583,586,589,591],{},[347,578,579],{},"UAT-03",[347,581,582],{},"Editor publishes a news post",[347,584,585],{},"Log in > Posts > Add new > add image > Publish",[347,587,588],{},"Post appears on \u002Fnews\u002F with image and correct date",[347,590],{},[347,592],{},[332,594,595,598,601,604,607,609],{},[347,596,597],{},"UAT-04",[347,599,600],{},"Mobile visitor finds opening hours",[347,602,603],{},"Open site on phone > menu > Contact",[347,605,606],{},"Hours visible without zooming; phone number is tappable",[347,608],{},[347,610],{},[332,612,613,616,619,622,625,627],{},[347,614,615],{},"UAT-05",[347,617,618],{},"Visitor switches language",[347,620,621],{},"Home > language selector > ES",[347,623,624],{},"Same page in Spanish; menu and footer translated",[347,626],{},[347,628],{},[332,630,631,634,637,640,643,645],{},[347,632,633],{},"UAT-06",[347,635,636],{},"Customer resets password",[347,638,639],{},"My account > \"Forgot password\" > email link",[347,641,642],{},"Reset email arrives; new password works",[347,644],{},[347,646],{},[287,648,649],{},"If the client can't describe the expected result of a scenario, that's a requirement that was never agreed, and it's better to find it now than after launch.",[297,651,653],{"id":652},"user-acceptance-testing-checklist-for-websites","User acceptance testing checklist for websites",[287,655,656],{},"Before the client starts, run through this list so the round tests the site, not the setup. It complements the scenarios: the scenarios check tasks, the checklist checks that everything needed to test those tasks is in place.",[658,659,662,672,678,684,690,696,702,708,714,720],"ul",{"className":660},[661],"contains-task-list",[488,663,666,671],{"className":664},[665],"task-list-item",[667,668],"input",{"disabled":669,"type":670},true,"checkbox"," QA finished and its issues fixed or listed",[488,673,675,677],{"className":674},[665],[667,676],{"disabled":669,"type":670}," Staging site has final content, not placeholders",[488,679,681,683],{"className":680},[665],[667,682],{"disabled":669,"type":670}," Emails from forms and orders arrive at the client's real addresses",[488,685,687,689],{"className":686},[665],[667,688],{"disabled":669,"type":670}," Payments run in test mode, with test card details shared with testers",[488,691,693,695],{"className":692},[665],[667,694],{"disabled":669,"type":670}," Every tester has a login with the right role, if the site has accounts",[488,697,699,701],{"className":698},[665],[667,700],{"disabled":669,"type":670}," Scenarios, deadline and sign-off criteria sent in one message",[488,703,705,707],{"className":704},[665],[667,706],{"disabled":669,"type":670}," One reporting channel agreed (no email, WhatsApp and calls in parallel)",[488,709,711,713],{"className":710},[665],[667,712],{"disabled":669,"type":670}," A way to tell bugs from change requests (a label or a separate list)",[488,715,717,719],{"className":716},[665],[667,718],{"disabled":669,"type":670}," The person who triages issues named, with a time to do it each day",[488,721,723,725],{"className":722},[665],[667,724],{"disabled":669,"type":670}," Re-test date booked for after the fixes",[297,727,729],{"id":728},"how-should-clients-report-uat-issues","How should clients report UAT issues?",[287,731,732],{},"Each issue should be one report with the scenario ID, what happened and what the tester expected, the page URL, the device, system and browser, a screenshot with the problem marked, and a severity: blocker (can't launch), major (must fix before launch) or minor (can wait). Clients forget half of these by email, so the format has to be easy or automatic.",[287,734,735],{},"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, and each vague report costs a round of questions. A complete one looks like this:",[737,738,744],"pre",{"className":739,"code":741,"language":742,"meta":743},[740],"language-text","UAT-02: Discount code not applied on mobile\n\nOn iPhone (Safari), after entering SPRING10 in the cart, the message\n\"Code applied\" appears but the total doesn't change.\nExpected: 10% off.\nURL: staging.example.com\u002Fcart\u002F\nSeverity: blocker\n","text","",[745,746,741],"code",{"__ignoreMap":743},[287,748,749,750,753,754,758],{},"Our ",[305,751,233],{"href":752},"\u002Fblog\u002Fwhat-to-put-in-a-bug-report\u002F"," has the full set of fields if you want to share a written format. A visual feedback tool fills most of them in for you. With ",[305,755,757],{"href":756},"\u002F","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.",[287,760,761],{},[762,763],"img",{"alt":764,"src":765},"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",[287,767,768,769,773,774,778],{},"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 the team's tracker: an issue in ",[305,770,772],{"href":771},"\u002Fjira-bug-tracking-tool\u002F","Jira",", a task in ",[305,775,777],{"href":776},"\u002Fasana-bug-tracking-tool\u002F","Asana",", ClickUp or Wrike, a card in Trello, or a message in Slack or Discord. For most website UAT, a marked-up screenshot with the browser data is all the developer needs to fix the issue.",[780,781],"blog-cta",{},[297,783,785],{"id":784},"when-is-uat-done","When is UAT done?",[287,787,788],{},"When the criteria agreed before testing are met: every scenario has been run at least once, no blocker or major issue is open, minor issues are listed with a fix date, change requests are logged and estimated separately, and the client confirms in writing. Without written criteria, UAT turns into an open-ended list of \"one more thing\".",[287,790,791],{},"Typical sign-off criteria for a website:",[658,793,794,801,807,813,819],{},[488,795,796,800],{},[797,798,799],"strong",{},"Coverage:"," all test scenarios have been run at least once.",[488,802,803,806],{},[797,804,805],{},"Severity:"," no open blocker or major issues.",[488,808,809,812],{},[797,810,811],{},"Minor issues:"," listed with an agreed fix date; they don't block the launch.",[488,814,815,818],{},[797,816,817],{},"Change requests:"," logged separately and estimated.",[488,820,821,824],{},[797,822,823],{},"Confirmation:"," the client approves in writing, by email or with the sign-off form above.",[287,826,827],{},"A simple sign-off email from the client is enough on most projects:",[737,829,832],{"className":830,"code":831,"language":742,"meta":743},[740],"We've completed acceptance testing of the new website on staging.\nAll scenarios UAT-01 to UAT-15 pass. The three minor issues in the\nlist will be fixed in the first week after launch. We approve the\nsite for go-live on 14 November.\n",[745,833,831],{"__ignoreMap":743},[287,835,836,837,841],{},"With criteria like these you have a clear line: the site does what was agreed, it launches, and anything new is the next phase. For the approval step itself, see our guide to ",[305,838,840],{"href":839},"\u002Fblog\u002Fclient-website-approval\u002F","client website approval",".",[297,843,845],{"id":844},"what-are-the-most-common-uat-mistakes","What are the most common UAT mistakes?",[287,847,848],{},"Five come up on most projects: starting before QA is finished, asking the client to \"have a look\" instead of giving scenarios, collecting feedback through five channels, mixing bugs with new requests, and leaving the round without a deadline. Each one makes UAT longer and turns a check on agreed tasks into a debate about taste.",[658,850,851,854,857,860,863],{},[488,852,853],{},"Starting before QA is finished: the client spends their time on bugs you should have caught.",[488,855,856],{},"No scenarios, just \"have a look\": you get opinions on colors instead of checks on tasks.",[488,858,859],{},"Feedback in five channels: email, WhatsApp, calls and comments on a PDF. Pick one channel and say so.",[488,861,862],{},"Mixing bugs and new requests: label them separately from day one.",[488,864,865],{},"No deadline: put UAT dates in the plan and in the contract.",[287,867,868],{},"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":743,"searchDepth":870,"depth":870,"links":871},2,[872,873,874,875,876,877,878,879,880],{"id":299,"depth":870,"text":300},{"id":320,"depth":870,"text":321},{"id":382,"depth":870,"text":383},{"id":479,"depth":870,"text":480},{"id":508,"depth":870,"text":509},{"id":652,"depth":870,"text":653},{"id":728,"depth":870,"text":729},{"id":784,"depth":870,"text":785},{"id":844,"depth":870,"text":845},"md",[883,886,888,891,894],{"question":884,"answer":885},"What is user acceptance testing in simple terms?","User acceptance testing is when the people who will own or use a website try it on real tasks and confirm it does what they asked for. It's the last check before launch: the agency prepares the scenarios and the staging site, the client runs them, and the round ends with the client's written sign-off.",{"question":321,"answer":887},"The client, their staff or a few real end users. The agency or developer writes the test scenarios with the client, prepares the staging site and fixes what comes up, but doesn't run the acceptance tests, because the people who built the site no longer see the problems a first-time user hits.",{"question":889,"answer":890},"How long should UAT take?","For a typical agency website, plan one to two weeks: a few days for the client to run the scenarios, time for fixes, and a short re-test of what changed. Put the dates in the project plan and the contract, because UAT without a deadline tends to drag on for months.",{"question":892,"answer":893},"Is there a UAT template in Word or Google Sheets?","Yes. This page offers an Excel test plan with scenarios, pass or fail tracking and a sign-off sheet, which opens in Google Sheets with File, then Import, and a Word sign-off form the client can fill in and sign once the acceptance criteria are met.",{"question":895,"answer":896},"What happens if the client finds new requirements during UAT?","Log them separately as change requests. UAT checks the scope that was agreed; new features are estimated and scheduled after launch or as a separate phase. Labelling bugs and new requests apart from day one keeps the round short and the launch date safe.",{"src":171,"card":172,"alt":208,"width":17,"height":18},{},{"title":204,"description":205},"User Acceptance Testing (UAT): Free Template & Examples","blog\u002Fuser-acceptance-testing-in-software-development",[210,211,212,213],"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 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 blocker or major issues.","vCz8uWP6_givx3hhdFVX5IqkQRVr1OOwyWsw5oGDKEo",1793059874482]