[ad_1]
What steps do you take when performing QA tests before launching, both for the front end and back end? Specifically, how do you handle front-end alignment issues and similar concerns? Are there any tools or methods you use?
[ad_2]What steps do you take when performing QA tests before launching, both for the front end and back end? Specifically, how do you handle front-end alignment issues and similar concerns? Are there any tools or methods you use?
[ad_2]
We use [Local](https://localwp.com/) for early development and if we are making major changes to a site. That way we don’t have to worry about the live site having any issues while working.
I use browserstack to test all sites before i make them live.
I use browserstack to test all sites before i make them live.
I sometimes use Automated Testing Selenium Chrome plugin. I wouldn’t call it QA but it can check some basic functions of site after a plugin/core upgrade/update.
We may have a more involved process than some lol:
1. Dedicated QA specialist checks in scoped browsers / devices using lambdatest. They also test backend for admin UX issues.
2. Scan site for WCAG 2.2 AA errors with SortSite tool; optionally do manual accessibility testing if it’s scoped
3. Test page performance
4. Scan site for security issues; update; implement security protocols
5. Test measurement plan (GTM; GA, etc…)
6. Check for server and JS errors in logs / console and remediate
7. Ensure all pages have appropriate metadata; schema, and images have alt text
8. That’s just a few things; we have a 60+ item list that is subdivided even further. We also use a bug feedback tool integrated with our PM system to collect all bugs directly there. This is nice b/c it includes all reporter browser details, console errors, etc… so no more, “What browser were you using?” questions.