UPWORD Consulting - Week 6

QA Testing


I want to help as many freelancers and agency owners generate high-value WordPress projects consistently and predictably and will keep the training and weekly support 100% free for as long as I can.

The resources in this course are crazy valuable ($15,000 worth of resources - but you won't pay anywhere near that), from all of my proposal templates, to legal agreements, to a fully built out WordPress agency site, these premium resources can help accelerate your growth.

You won't find another course like this that is so affordable and packed with so much valuable content. Unlock the resources today!

Learn More

Hey everyone welcome to week six, and module three, and in this module we're going to be covering quality assurance testing, because we need to make sure that we've found and fixed all issues on the WordPress side and the front end side for asking for final approval to go live, and really before we ask for final payment is a critical step to keeping your client trusting you and making sure that your work quality is something that you can take pride in.

So where do we start when the WordPress developers, let me know that the site is ready for initial review, I go through the site personally on the front end, and on the WordPress side of things, to make sure there are not any major glaring issues.

So the very first thing I do is take a look at the front end templates, meaning the different pages blogs about us whatever might be its own template. It just makes sure that there aren't any glaring bugs, because this is where the client is going to spend the majority of their time with WordPress front end can change a bit because some of the nuances and the details of just shifting things around once WordPress. WordPress is integrated. And I like to give it a once over four major issues before I update the client at all.

From there, I log into WordPress for the first time and start to poke around and really all I start is with the homepage and start swapping out text and images, and making sure that WordPress is functioning properly, that I have editing access to everything that the client will need, and make sure that the front end of the site doesn't break 99% of the time I find issues for the developers to fix so it's really just me logging in, poking around making sure that I can change the logo change images swap out content, hit save, preview, just all the basic stuff. I like to do and start swapping in the real live content, whether that's from the client, or from writing your content writer.

So once I've done my basic due diligence for the first phase, the developers have fixed the bugs. I then test each item that I sent over them and I just want to make sure that they've actually fixed, what they said they have.

Once this is complete, I then post a base camp for the client to review the initial Wordpress version of the site, as they'll most likely have some changes with images and copy and some most likely minor tweaks.

Also, this is where I'm super generous with edits, anything major with the design or the layout of the page. And the reason why is because this is where generosity helps me in the long run. Clients are usually in the stage, but typically feel with all the content they need to gather and send us pretty much all of my clients wait until the very last minute, so I try to continue to build trust and loyalty by just taking care of edits that might be slightly out of scope. This has paid dividends for me and I highly recommend doing this, within reason of course, whatever that might look for you, but I can tell you that just, again, treating your clients as humans and what would you want another invoice or hey let me just take care of this, obviously, you've got to set boundaries but I highly recommend that you be a bit more generous with some of these edits and it'll pay dividends in the long run. So once the client is reviewing the desktop site, providing content and edits.

This is what I typically start going through the site on mobile, and I use a few different tools for this, and I'll share the links in the resources section below. But at the end of the day it's always best to test on your actual phone so I pull out my iPhone and I just go kind of template by template of what I did on desktop, and I find the issues and log them for my developers, obviously you're not going to have every phone to physically test with. And that's where I utilize some of those tools down below so I can see various browsers and screen resolutions pretty easily and get the majority of them knocked out. So, after mobile has been tested and working,

I then go through the site in the major browsers and make sure that there aren't any cross browser bugs because there always is, especially with Safari, and thank God, Internet Explorer is not so much of a thing anymore but Firefox, Safari and edge are gonna give you problems Chrome is my favorite browser and the easiest to work with but you need to make sure that you're testing for all these, I test on Chrome, Firefox, Safari and edge, and if I find any issues. I then send these over to my developers and edits from the client. So you can see I'm kind of pushing the ball forward as a client's working on the desktop version, I'm already starting on mobile.

Now, whenever I'm getting ready to launch a site I have people on my team to do the same exact thing and go through and find bugs as developers are notorious for missing issues that are painfully obvious to us non developers. So, if you're a one man woman shop, I definitely recommend finding an offshore QA tester to go through each of your projects with a fine tooth comb. This just helps you get a fresh set of eyes when I'm staring at a site for so long stuff that is obvious gets missed. So I'd like to have someone go through fresh set of eyes that isn't quite is tied to the project and the design as you are, just to have them go through and see what they find.

And then if you end up working with ALOA for WordPress development they have a dedicated QA resource for you so you won't have to focus so much on bugs, and it's another reason why I recommend them and use them for my WordPress projects, however, still make sure that I've personally gone through the site, enough to ensure that nothing got missed. And the reason why is that I just need to make sure that when I speak to the client I kind of know where everything is how everything functions in a basic way so that I'm confident in our work and I know if an issue arises, I kind of know the general direction of where I need to go immediately. So I like to be familiar with my own project and not stay out of it too much, and that's pretty much how I handle QA testing.

And once the client approves the Go Live and I've received final payment again do not launch anything until you get final payment.

I'm going to walk you through the checklist I personally use to make sure that I'm ready for the switch from the dev server to the client server. And also we're going to be replacing the current site so from backups to SEO stuff, just making sure that we follow this plan every single time. That's going to be included in the next module, I'm going to walk you piece by piece. And you will also have that checklist of download that you can use for every single one of your projects. I will see you on the next module.