{"id":13409,"date":"2026-02-23T13:28:18","date_gmt":"2026-02-23T13:28:18","guid":{"rendered":"https:\/\/wpm.si\/?p=13409"},"modified":"2026-02-23T13:28:18","modified_gmt":"2026-02-23T13:28:18","slug":"website-development-qa-testing-and-final-review","status":"publish","type":"post","link":"https:\/\/wpm.si\/en\/wordpress-development\/website-development-qa-testing-and-final-review\/","title":{"rendered":"Website development: QA, testing, and final review"},"content":{"rendered":"<p>Once <a href=\"https:\/\/wpm.si\/en\/wordpress-development\/website-development-development-phase\/\">website development<\/a> is complete, the website enters one of the most critical stages of our process: <strong>structured quality assurance (QA) and validation<\/strong>. At <a href=\"https:\/\/wpm.si\/en\/\">WPM<\/a>, QA is not an informal check or a quick pass through the website \u2014 it is a clearly defined phase with established procedures, tools, and internal standards. The focus shifts from building to verifying that <strong>every element behaves exactly as intended in real-world conditions<\/strong>.<\/p>\n<h2>Internal quality assurance based on a structured checklist<\/h2>\n<p>Our QA process is built around a detailed <strong>internal checklist<\/strong> that we use across all projects. To manage this effectively, we use <a href=\"https:\/\/asana.com\/\" target=\"_blank\" rel=\"noopener\"><strong>Asana<\/strong><\/a> to distribute tasks across our entire team. By assigning each point to the specific <strong>developer, designer, SEO expert, or content specialist<\/strong> best suited for the job, we can precisely track progress, monitor tasks, and ensure no detail is overlooked.<\/p>\n<blockquote><p>While this checklist is also used during website launches, QA and launch preparation are closely connected \u2014 the same checklist covers both <strong>pre-launch validation<\/strong> and <strong>launch-readiness checks<\/strong>. This ensures consistency, repeatability, and a high level of reliability across all projects.<\/p><\/blockquote>\n<p>During internal QA on the development environment, we systematically validate:<\/p>\n<ul>\n<li><strong>Functionality<\/strong> \u2013 forms, buttons, navigation, filters, checkout flows, and integrations<\/li>\n<li><strong>User flows and links<\/strong> \u2013 verifying that no broken paths, incorrect URLs, or development references remain<\/li>\n<li><strong>Responsive behavior<\/strong> \u2013 layout integrity across devices, breakpoints, and orientations<\/li>\n<li><strong>Content consistency<\/strong> \u2013 headings, spacing, formatting, translations, and missing or placeholder content<\/li>\n<li><strong>Technical setup<\/strong> \u2013 plugin configuration, structured data, SEO fundamentals, security headers, and system limits<\/li>\n<\/ul>\n<p>We actively test the website as real users would \u2014 navigating the interface, submitting forms, interacting with dynamic elements, and deliberately exploring edge cases. QA is treated as a <strong>validation phase<\/strong>, not a discovery phase.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-13438\" src=\"https:\/\/wpm.si\/wp-content\/uploads\/2026\/02\/wpm_qa_checklist.jpg\" alt=\"\" width=\"1820\" height=\"1024\" srcset=\"https:\/\/wpm.si\/wp-content\/uploads\/2026\/02\/wpm_qa_checklist.jpg 1820w, https:\/\/wpm.si\/wp-content\/uploads\/2026\/02\/wpm_qa_checklist-711x400.jpg 711w, https:\/\/wpm.si\/wp-content\/uploads\/2026\/02\/wpm_qa_checklist-1400x788.jpg 1400w, https:\/\/wpm.si\/wp-content\/uploads\/2026\/02\/wpm_qa_checklist-768x432.jpg 768w, https:\/\/wpm.si\/wp-content\/uploads\/2026\/02\/wpm_qa_checklist-1536x864.jpg 1536w\" sizes=\"auto, (max-width: 1820px) 100vw, 1820px\" \/><\/p>\n<h2>Mobile-first testing in practice<\/h2>\n<p>Mobile testing is a core part of our QA process, not an afterthought. We validate touch interactions, spacing, readability, performance, and navigation clarity across multiple screen sizes. This goes beyond visual checks \u2014 we test usability, interaction behavior, and real scrolling and tapping patterns. <strong>Responsiveness is confirmed through hands-on testing, not assumed.<\/strong><\/p>\n<h2>Performance, security, and monitoring tools<\/h2>\n<p>As part of QA, we use a combination of external tools and internal systems to validate performance, stability, and security:<\/p>\n<ul>\n<li><a href=\"https:\/\/pagespeed.web.dev\/\" target=\"_blank\" rel=\"noopener\"><strong>Google PageSpeed Insights<\/strong><\/a> for performance, Core Web Vitals, and loading behavior<\/li>\n<li><b>A custom SEO audit solution<\/b>\u00a0for technical SEO checks, site health, and post-deployment monitoring<\/li>\n<li><a href=\"https:\/\/bugbug.io\/\" target=\"_blank\" rel=\"noopener\"><strong>BugBug<\/strong><\/a> for automated and repeatable functional testing scenarios<\/li>\n<li><a href=\"https:\/\/sucuri.net\/\" target=\"_blank\" rel=\"noopener\"><strong>Sucuri<\/strong><\/a> for security validation \u2014 typically applied after launch, as development takes place on a secured staging environment<\/li>\n<li><strong>Custom internal monitoring solutions<\/strong> developed in-house to track errors, failures, and unexpected behavior<\/li>\n<\/ul>\n<p>This combination allows us to identify issues early, confirm fixes reliably, and maintain a high level of technical confidence before client review.<\/p>\n<h2>Client review on the development domain<\/h2>\n<p>Once internal QA is completed, the website is shared with the client on the development domain. By this stage, the website has already passed functional, technical, and usability validation. Client feedback at this point is therefore typically focused on <strong>fine-tuning, content adjustments, or final refinements<\/strong> rather than structural changes.<\/p>\n<h2>From QA to launch<\/h2>\n<p>At this point, the website is technically validated, performance-checked, and ready for real traffic. While QA and launch preparation overlap through our checklist, the actual <strong>launch process<\/strong> involves additional steps and safeguards. In the next article, we\u2019ll walk through how we move a website from development to production in a controlled and secure way.<\/p>\n<a href=\"https:\/\/wpm.si\/en\/inquiry\/\" class=\"button primary is-primary is-medium\">\n\t\t<span>Send an inquiry<\/span>\n\t<\/a>\n\n","protected":false},"excerpt":{"rendered":"<p>Before launch, every website development project goes through our structured quality assurance process. Using internal checklists, performance tools, security validation, and real-world testing scenarios, we ensure technical stability, usability, and launch readiness.<\/p>\n","protected":false},"author":1,"featured_media":13436,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[],"class_list":["post-13409","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress-development"],"_links":{"self":[{"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/posts\/13409","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/comments?post=13409"}],"version-history":[{"count":3,"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/posts\/13409\/revisions"}],"predecessor-version":[{"id":13440,"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/posts\/13409\/revisions\/13440"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/media\/13436"}],"wp:attachment":[{"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/media?parent=13409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/categories?post=13409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpm.si\/en\/wp-json\/wp\/v2\/tags?post=13409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}