Let’s face it; we all make mistakes, right? Also, I feel it is important that we need to not be afraid of making mistakes – especially for those of us (raises hand) who excel at learning from those mistakes.
However, that doesn’t mean that we shouldn’t endeavor to avoid making them. Learning from mistakes is great, but it’s even better to avoid the ones you can. So… how does one go about developing their own successful quality control process?
I’m not 100% certain myself, so I figured maybe we could learn about this vital subject together. What do you say?
Like so many other things in 2019, I started this journey with a Google search. Something super simple:
Apparently ‘web development’ is the same as ‘software development’ according to Google. Let’s be a bit more specific:
BINGO! This looks promising. It’s not super recent, but it may help us get the roll rolling here.
*30 minutes go by*
Okay; this article contains a lot of useful information. It’s hosted by a site call conversionxl, and as the domain name would suggest, they want the site to bring in sales, and it needs to work correctly to do that, and bing-bang-boom – testing.
So, with the help of this article, I can start developing my QA / QC process. What will mine look like? I don’t know just yet; but I’m guessing it will be something like this:
1. Checking for breakpoints & errors
2. viewing at different resolutions and on different devices. For me this will mean covering about three breakpoints. It’s important to use different device types, as a typical phone screen resolution may not look the same on a phone as it does on a monitor.
3. Testing for speed. Does it take a long time to load? Why?
4. Solicit input from a test group. What is their feedback like?
Anywho, I think I’ll do a part two to this just do it doesn’t get too long. Next time, we’ll check out some additional articles and see if we can’t flesh out this process to a satisfactory level. Until next time!