WordPress QA Testing and Bug Fixes
$30-250 USD
Posted 1 minute ago
•
Ends in 6 days
$30-250 USD
Paid on delivery
I need a QA / test automation specialist to fully test my WordPress website on desktop and mobile, fix small bugs, and report the results. The website link will be shared with the selected freelancer after hiring. The site includes choir search and filters, free taster booking, membership sign-up, forms, and general navigation. Scope of testing: - Pages and navigation: every page, menu, button and link. Check for broken links, 404 errors and missing images. - Choir search and filters: search by keyword and location, combine filters, check that empty results show a sensible message and that results are correct. - Free taster booking flow: complete the booking from start to finish, check form validation and the confirmation message. - Membership flow: sign-up, login, logout, password reset, and access to members-only pages. - Forms: required fields, error messages, successful submission, and spam protection. - Responsiveness: desktop (Chrome, Firefox, Safari, Edge) and mobile/tablet (iOS Safari, Android Chrome). - Basic checks: JavaScript console errors, slow-loading pages, and obvious layout breaks. Bug fixing: - Fix small issues such as CSS and layout problems, broken links, form settings, and plugin configuration. - Report anything that would take more than about 30 minutes before working on it. It will need my approval. - Make fixes on a staging copy first, then move them to the live site. Access provided after hiring: - WordPress admin access and a staging site - Test details for booking and membership. Please don't send real payments or use real customer data. Deliverables: 1. A test report (spreadsheet or document) showing each test, pass or fail, and screenshots of failures 2. A list of the bugs fixed, with before and after notes 3. A list of remaining issues and recommendations 4. Your automation scripts (Playwright preferred) so I can rerun the tests later Requirements: - Proven experience with WordPress testing and debugging - Hands-on experience with Playwright, Selenium, Cypress or similar tools - Ability to start immediately Timeline: 6 hours. Testing and the report come first, then the fixes. To apply, please include: - A short summary of similar WordPress QA work you've done - Which tool you'll use and why - The first 2-3 things you would test on this site
Project ID: 40817244
About the project
47 proposals
Open for bidding
Remote project
Active 4 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
47 freelancers are bidding on average $115 USD for this job


Hello, WordPress development backed by 15+ years of experience makes me well suited to test and fix your site’s booking, membership, forms, navigation, and responsive behaviour. As the founder of A4Logic, I work across WordPress, PHP, JavaScript, and CSS, giving me the technical background to identify whether an issue comes from the frontend, form setup, plugin configuration, or custom code. I can provide thorough QA coverage for desktop and mobile flows, including choir search and combined filters, taster booking validation and confirmation, membership access, password reset, form errors, broken links, missing images, console errors, and layout problems. I will document pass/fail results with screenshots, record before-and-after fixes, and separate larger remaining issues for approval. I can also produce reusable automation scripts using a suitable browser-testing approach. I am ready to apply my WordPress debugging and QA-focused development skills to deliver a clear test report and reliable small fixes within the project scope. Thanks!


Hi there, I understand you need a thorough QA test for your WordPress website across desktop and mobile devices, specifically focusing on choir search filters, booking forms, membership sign-ups, and general navigation. My goal is to ensure a flawless user experience by identifying and fixing any underlying bugs before they impact your users. My execution plan involves a comprehensive manual testing phase using real browsers and devices to simulate actual user journeys through your filters and forms. I will meticulously document every issue found in a clear report, followed by direct intervention to fix CSS styling issues, JavaScript conflicts, or PHP logic errors within your WordPress environment. I will also verify cross-browser compatibility to guarantee consistent performance everywhere. With over five years of full-stack development experience, including deep expertise in JavaScript, CSS, and web application debugging, I can quickly pinpoint the root cause of CMS-related glitches. I can comfortably deliver the complete testing report and all necessary bug fixes within 3 days. Let us connect via chat so I can review your site link and get started right away. Regards Khorshed Alam


Hello, I can thoroughly test your WordPress site across desktop and mobile, covering navigation, choir search and filters, taster booking, membership access, forms, responsiveness, console errors, and performance issues. I will use Playwright because it supports reliable cross-browser automation, reusable test scripts, screenshots, and clear reporting. I would first test the membership authentication flow, then the booking and form validation journeys, followed by choir search/filter combinations and responsive layouts. I will work on staging, document every result with evidence, fix approved small issues, and provide scripts, before/after notes, remaining issues, and recommendations. One useful improvement is adding reusable test data and stable selectors for future reruns. Regards Muhammad


Hi there, You need thorough QA testing on your WordPress site, ensuring everything from navigation to membership flows works seamlessly. My experience in testing WordPress sites and fixing bugs makes me well-suited for this project. How I would approach it: - Start with a comprehensive check of the navigation and all links to ensure there are no broken elements or errors. - Test the choir search and filters, validating the results and confirming appropriate messaging for empty searches. - Execute the free taster booking process completely, checking form validations and confirmation messages along the way. - Assess responsiveness across the specified browsers and devices to ensure a consistent user experience. I am well-versed in WordPress QA and have used Playwright for automation tasks in similar projects. My process involves detailed documentation of each step, so you can easily track fixes and testing outcomes. What unique challenges or features should I focus on during testing to ensure the best user experience? I look forward to delivering a thorough and effective testing outcome for your site.


Hi, I'm a senior developer with 10+ years of experience and I've spent the last several years doing exactly this kind of WordPress QA work—testing search and filter logic, membership flows, form validation, and cross-browser responsiveness on production sites. I know the common failure points and how to catch them systematically. I'll start by running through every page, menu, link and form you've listed, testing on desktop (Chrome, Firefox, Safari, Edge) and mobile (iOS Safari, Android Chrome) using Playwright, which gives me reliable automation scripts you can rerun later without needing me. I'll test the choir search and filters with real data to verify results are correct, walk through the full taster booking and membership sign-up flows including password reset, check all forms for validation and error handling, and flag any JavaScript console errors or layout breaks. I'll document everything in a spreadsheet with screenshots of failures, then move to fixes on staging before touching the live site—anything that looks like it'll take more than 30 minutes gets flagged to you first. The test report comes first, then fixes, then a list of remaining issues and recommendations along with your Playwright scripts so you can run the tests again anytime. I'll stay available after delivery for any adjustments or questions that come up.


I have hands-on WordPress QA and debugging experience and would use Playwright for reliable cross-browser automation, reusable test scripts, and clear reporting. I’d first test the choir search/filter combinations, then the taster booking flow and membership authentication, followed by forms, responsive layouts and console errors. I’ll test on staging first, fix approved small issues, and provide the requested report, screenshots, before/after notes and reusable automation scripts. Best Regards, Muhammad


My experience building website-audit and problem-detection systems, supported by JavaScript, PHP, and CSS skills, is directly relevant to testing your WordPress site’s navigation, forms, filters, and responsive layouts. I can identify broken links, console issues, validation problems, CSS defects, and configuration errors, then apply appropriate small fixes while keeping the findings clearly documented. For browser automation, I would use Playwright because it supports repeatable end-to-end checks across Chromium, Firefox, and WebKit, making it well suited to your choir search, taster booking, membership, login, and form flows. I would first test the main navigation and all key links, the combined choir search/location filters including empty results, and the complete booking and membership journeys with validation and confirmation behavior. My deliverables would include a pass/fail test report with screenshots, fixed-bug notes, remaining issues and recommendations, plus reusable automation scripts. I can focus on testing and reporting first, then handle approved small fixes on staging before deployment. I would be glad to bring my JavaScript, PHP, and CSS troubleshooting skills to this QA assignment.


Your whole site checked on desktop and phones, with small fixes made on staging before they touch live. That's the kind of careful WordPress work behind my 5.0 from 29 reviews. I'll use Playwright, as you prefer. One script runs Chrome, Firefox, Safari's engine and mobile sizes, screenshots every failure for the report, and you can rerun it later with one command. First I'd run the free taster booking end to end with your test details. Next is keyword plus location search with combined filters, including one search that should return nothing. Third is sign-up, login and password reset, because a reset email that never arrives is the most common silent failure. On similar work I copied a live WordPress site to staging and moved changes back safely, 5★: https://www.freelancer.com/projects/php/Production-site-replication-process Is your staging site a fresh copy of live, or should I sync it first?


I can thoroughly test your WordPress site across desktop and mobile, document every result, and fix approved small issues safely on staging before deployment. I would use Playwright because it supports reliable end-to-end flows, cross-browser testing, mobile emulation, screenshots, and reusable automation scripts. I’ll organize the work around your six-hour timeline, prioritizing testing and the report before fixes. My first checks would be: 1. Validate navigation, links, images, console errors, and key page loading behavior. 2. Test choir search with keywords, locations, combined filters, and empty-result handling. 3. Complete the booking and membership journeys, including validation, authentication, password reset, permissions, and confirmations. You’ll receive a clear pass/fail report with screenshots, fixed-issue before/after notes, remaining risks, recommendations, and Playwright scripts for future reruns. I’ll use only staging and provided test details, never real payments or customer data, and will request approval for issues requiring more than approximately 30 minutes.


Mobile and desktop testing on the same WordPress site usually turns up different bugs entirely, especially with CSS breakpoints and form behavior. I would run through the site manually first, log every issue with screenshots, then build Selenium scripts for the critical flows so you can re-test after fixes fast. Can start today, first pass ready in 2 days. These numbers are based on the post as written, we will refine them after a quick scope chat. Want me to send a plan?


Hi, I’ve reviewed your WordPress QA Testing and Bug Fixes and understand what you’re looking to achieve. I can help you handle the required work with a clean, reliable, and professional approach. I have experience with PHP, JavaScript, Testing / QA, WordPress, CSS, Test Automation, Website Testing, MQTT, Selenium, Web Testing and can work effectively with your existing setup, requirements, and workflow. I’ll focus on proper implementation, responsive functionality, attention to detail, and thorough testing to make sure everything works as expected. I’ll also make sure the completed work is aligned with your requirements rather than just providing a quick or temporary solution. I’m available to start immediately and can work according to your required timeline. Best regards, Khadija Tul Kubra


My 7+ years of full-stack web development experience with WordPress, JavaScript, and CSS makes me well suited to test both your website’s functionality and its responsive presentation. I build and work across desktop, mobile, and tablet experiences, so I can identify navigation, layout, form, and interaction issues—not just surface-level visual defects. I can thoroughly review the choir search and filters, free taster booking, membership access, forms, links, responsive layouts, JavaScript behaviour, and obvious performance issues. My WordPress and CSS experience also enables me to fix small layout, link, form-setting, and configuration bugs carefully on staging before they are moved live. I will provide clear pass/fail reporting, screenshots, fixed-issue notes, remaining recommendations, and automation scripts where supported by the available testing setup. The first priorities would be the complete booking flow, membership sign-up/login and access control, and choir search with combined filters and empty-result handling. I communicate well, follow instructions closely, and would be glad to apply my WordPress and web development experience to deliver a useful QA report and dependable fixes within the available timeline.


Hello I think you want a reliable QA pass that checks the complete WordPress experience before small fixes are moved to the live site. I would start with the choir search and combined filters, then test the free taster booking and membership flows, including validation, confirmations, login and password reset. I would use Playwright because it can automate repeatable browser tests and capture screenshots when something fails. I would also check navigation, responsive layouts, console errors, broken links and form behaviour across the available browsers and devices. Testing and the report would come first; I would document each pass or failure, fix only small approved issues on staging, and flag anything likely to exceed 30 minutes before proceeding. I would include the reusable test scripts, fix notes and remaining recommendations. Are test accounts and booking scenarios ready for the six-hour testing window? Looking forward to work with you. Thanks.


Hi there, Can you confirm whether the staging copy already mirrors the live plugins and theme settings, and are there any known broken areas you want prioritized first? Which form/plugin stack powers the booking, membership, and contact forms, and should the tests cover any custom redirects or email rules? The main challenge here is checking the full WordPress user flow without missing small issues that only appear across browsers or on mobile. I would use Playwright because it can cover desktop and mobile viewports, repeat the same tests across browsers, and save clean screenshots and traces for failures. Which form/plugin stack powers the booking, membership, and contact forms, and should the tests cover any custom redirects or email rules? A key risk is that some bugs may be tied to plugin settings or theme overrides, not just visible CSS. I would verify each issue on staging first, note anything that needs approval beyond a quick fix, then move only safe changes to live after rechecking the affected flow. The first pass would focus on navigation, search and filters, and the free taster booking path, then membership login and form validation. After that, I would run responsive checks, review console errors, and deliver the report, bug list, and rerunnable scripts in a clear format. Best, Hlib


I’ve tested and repaired WordPress membership and booking sites, including form validation, plugin configuration, responsive layouts, and documented regression results. For this project, the key is Playwright because it creates repeatable browser checks for your choir search, booking, and member journeys across desktop and mobile viewports. I’ll first test navigation and broken assets, then combine choir keyword/location filters, and complete the taster booking and membership flows using safe test data. I’ll log pass/fail evidence with screenshots, fix approved small issues on staging, and verify each fix before live deployment. You’ll receive the report, before-and-after fix notes, remaining recommendations, and reusable Playwright scripts. Thanks, Kittipong


Hello. It sounds like ensuring a seamless user experience on your WordPress website is a priority, especially with features like choir search and booking flows. A critical aspect to focus on will be the functionality of the choir search filters, as any issues here could impact user satisfaction significantly. I have tested and debugged several WordPress sites, particularly focusing on user flows and responsiveness. One key insight for your project is the importance of not only identifying bugs but ensuring that the user journey remains intuitive throughout different devices and browsers. To start, I would first test the membership sign-up process, followed by the free taster booking flow, and then check all navigation elements for broken links. What specific metrics or user feedback do you currently have that could guide the testing process? Thanks, Artiom.


Hi! I can fully test your WordPress site on desktop and mobile, then fix the small issues I find. I’d start by reviewing the staging site, then map the booking, membership, search, and forms flow before running Playwright checks. My background in JavaScript and Android testing helps me build reliable Playwright scripts and catch layout, navigation, and form problems quickly. I’ll fix what’s safe on staging first, then prepare a clear report with screenshots and remaining risks. I’ll handle planning, testing, fixes, and handover, and I’ll share the rerunnable automation scripts too. Ruslan Which browsers and device sizes should I prioritize for the first QA pass?


Hi, I understand you need thorough WordPress QA across desktop and mobile, with bug fixes and a clear report to guide next steps. I’ve done similar WordPress QA work, from end-to-end test planning to regression checks on live sites. Execution approach: I’d start by validating core flows, navigation, search, booking, and membership, against real usage, then stabilize flaky parts with focused Playwright tests and lightweight CSS fixes on staging before going live. I’ll document each issue with before/after notes and screenshots. One technical risk: asynchronous UI prompts may cause flaky tests until timing is tuned. Two clarification questions: 1) What is the test data policy for staging vs production? 2) Who owns the staging environment and the door between staging and live deployment? If we're aligned, I can outline the implementation phases before kickoff. Best regards, Brandon


Hi, I'm Christian, a full-stack developer specializing in WordPress QA testing, bug fixes, and test automation. You need a thorough QA pass on your membership and booking site to catch broken links, form issues, responsive design problems, and JavaScript errors. I'll deliver a clear test report, fix issues on staging first, and create automation scripts your team can rerun without rehiring. My process: I'll review your site structure and credentials, then systematically test pages, navigation, choir search, booking flows, membership login, access controls, and form validation. I'll test Chrome, Firefox, Safari, and Edge on desktop, plus iOS Safari and Android Chrome on mobile. Using Playwright for automation, I'll log all findings, fix minor issues like CSS and broken links on staging, and request approval for larger changes before going live. My focus: Membership and booking flows must work reliably across all browsers and devices—login state, password reset, and member-only access are critical to your business. I'll flag anything uncertain and ask before fixing to avoid scope creep. I'm ready to start immediately. Let's discuss the details. Thanks, Christian.


Hi, Your choir search, taster booking, and membership flows need to work flawlessly on desktop and mobile before visitors hit them. I'll test each flow end to end, log every failure with screenshots, and fix small CSS, link, and form issues on staging first. With 7+ years in web development, I'll use WordPress, PHP, and JavaScript debugging to check console errors, validation, and responsive layouts across the browsers you listed. Which browser and device combination is the highest priority for your visitors? Regards, Sakline P.S. Sharing staging access and the booking test details early will let me start the flow testing right away, and I'll include a short checklist of the first issues to verify.
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗