TRASCRIZIONE 🔗
WEBVTT
00:00:05.759 --> 00:00:10.320
With AI writing so much code, do we even need a quality assurance department?
00:00:10.720 --> 00:00:15.839
If I can ask my AI to evaluate code, what's the purpose of having a QA person around?
00:00:16.160 --> 00:00:23.280
Now right up front, I'm gonna tell you that yes, QA is absolutely valuable and not replaced by AI.
00:00:23.519 --> 00:00:29.120
And as an aspiring developer, going into a QA role might be a good choice for you.
00:00:29.359 --> 00:00:37.840
But let's talk about why QA is valuable still and why AI can't just replace them in today's episode of DevQuestions.
00:00:45.920 --> 00:00:48.640
Software development is more than just writing code.
00:00:48.799 --> 00:00:50.240
So let's talk about the rest of it.
00:00:50.399 --> 00:00:56.320
Specifically, let's talk about quality assurance team members and why they are still valuable.
00:00:56.560 --> 00:01:02.159
And let me start off by saying that not every company can afford a dedicated QA person or team.
00:01:02.320 --> 00:01:04.400
I've been on a number of those teams.
00:01:04.719 --> 00:01:09.359
But in that case, you absolutely need someone who can fill that role.
00:01:09.680 --> 00:01:13.680
So the question becomes: what does a good QA person do?
00:01:13.840 --> 00:01:21.040
And I did say good because not every person in QA does a good job, just like not every developer does a good job.
00:01:21.200 --> 00:01:23.680
But let's talk about what a good QA person does.
00:01:23.760 --> 00:01:25.840
And I put it into four categories.
00:01:26.079 --> 00:01:33.040
The first category is ensure software quality, not necessarily make software quality.
00:01:33.120 --> 00:01:36.319
Again, QA people are not necessarily developers.
00:01:36.560 --> 00:01:42.079
They can be, and I find that's often valuable if they have some development skills.
00:01:42.400 --> 00:01:47.359
But they're ensuring software quality by doing things like testing.
00:01:47.599 --> 00:01:52.560
They're looking at regression and making sure that they prevent regression in their code.
00:01:52.719 --> 00:02:00.480
By the way, if you don't know what regression is, it means maybe you fix one problem, but you solve or you cause other problems while you do so.
00:02:00.640 --> 00:02:01.680
That's regression.
00:02:01.760 --> 00:02:04.159
Um, something that was working isn't working anymore.
00:02:04.400 --> 00:02:09.680
So they they work on testing, they work on preventing regression, they work on identifying defects.
00:02:09.919 --> 00:02:15.439
They try and pick apart your code, how it works, and find all the issues.
00:02:15.599 --> 00:02:17.520
So they ensure software quality.
00:02:17.599 --> 00:02:19.039
That's number one category.
00:02:19.199 --> 00:02:25.280
Number two is they understand the requirements, which sounds weird, right?
00:02:25.360 --> 00:02:26.479
That's that's one of their jobs.
00:02:26.639 --> 00:02:27.919
Yes, absolutely.
00:02:28.159 --> 00:02:31.599
They need to be the ones that really understand the requirements.
00:02:31.759 --> 00:02:35.360
Now, developers, we should know the requirements backwards and forwards.
00:02:35.840 --> 00:02:42.400
But the QA person needs to know from the user perspective what the requirements are.
00:02:42.639 --> 00:02:46.479
And a lot of times the requirements don't get put into a document.
00:02:46.639 --> 00:02:52.960
And yes, I know some people love to have these huge long documents that explain everything about the system.
00:02:53.520 --> 00:02:54.639
It's never enough.
00:02:54.879 --> 00:02:58.319
It's never enough, it's never right, uh, it's never complete.
00:02:58.639 --> 00:03:02.960
Understanding the requirements from the user's perspective is really important for QA.
00:03:03.120 --> 00:03:08.159
Now, this may be where there's a hybrid role with the business analyst.
00:03:08.479 --> 00:03:13.759
Business analysts and QA people are different sometimes and sometimes the same person.
00:03:14.000 --> 00:03:16.719
Um, I've I've seen pros and cons for both.
00:03:16.960 --> 00:03:22.319
But if they're in a hybrid role, this is where they also have gathered the requirements in the first place.
00:03:22.560 --> 00:03:29.120
They're the person that sits between the user and the developer, and they know the role really well.
00:03:29.759 --> 00:03:32.479
So either way, they understand the requirements.
00:03:32.639 --> 00:03:36.400
This is really important because they're the ones that are gonna test the requirements.
00:03:36.560 --> 00:03:40.400
They're the ones that are gonna validate if the requirements are being met.
00:03:40.560 --> 00:03:48.879
They're a person outside of the developer who knows what should happen and verifies it does happen.
00:03:49.120 --> 00:03:52.000
Because too often as developers, we're really close to the issue.
00:03:52.159 --> 00:03:54.479
And you know, we've got our nose right next to the code.
00:03:54.639 --> 00:04:00.560
We're we're working on making the code, we kind of lose track a bit of the overall goal sometimes.
00:04:00.719 --> 00:04:06.800
Or we get you know working on our feature and somebody else working on their feature, and we kind of mash all together and say, hey, there you go.
00:04:06.960 --> 00:04:11.599
And there's no one looking at it and says, wait, wait, wait, here's the overall requirements.
00:04:11.759 --> 00:04:13.039
We're missing some.
00:04:13.280 --> 00:04:16.480
Or these things work, but they don't work well together.
00:04:16.720 --> 00:04:19.360
Like understanding the requirements is really important.
00:04:19.600 --> 00:04:24.480
And then understanding how to evaluate if you're meeting those requirements is really important.
00:04:25.279 --> 00:04:31.519
Number three, kind of goes with number two, but number three category is they represent the user.
00:04:31.839 --> 00:04:37.680
And that means they're looking for things like is the is the application intuitive?
00:04:38.240 -->
Load full transcript
00:04:50.480
Your application can work, it can meet all the requirements, and it might not be intuitive, which means it really should fail QA because the user has to be able to use it.
00:04:50.639 --> 00:04:59.519
I was talking to a person on YouTube today about this where they said, Hey, I think I've built the right user interface, but the user says they want something different.
00:04:59.680 --> 00:05:00.879
What do I do?
00:05:01.199 --> 00:05:06.399
Well, at the end of the day, the user is the one using your application.
00:05:06.639 --> 00:05:17.040
I built systems that that worked and that were logical and that had all the right pieces and they weren't intuitive or they didn't behave as expected.
00:05:17.120 --> 00:05:20.560
That's another part of this, is they check to make sure it behaves as expected.
00:05:20.720 --> 00:05:22.720
For example, tab order.
00:05:22.879 --> 00:05:26.560
This is one that I used to get wrong every once in a while when I was a young developer.
00:05:26.720 --> 00:05:32.639
Uh I was using uh VB6 when I was first building applications, and you would drag things out of the form.
00:05:32.720 --> 00:05:40.639
But if you drag things in the form in the wrong order, well, it would assign tab order based upon what the last tab item was that was put in the form.
00:05:40.879 --> 00:05:46.879
So I'd I'd put things in the form and then drag and rearrange them, but the tab order wouldn't rearrange with it.
00:05:47.120 --> 00:05:51.839
So maybe you know, a simple example, you might be in a uh a field that asks you for your address.
00:05:51.920 --> 00:05:53.839
So it's street address, city, state, zip.
00:05:54.079 --> 00:05:58.319
And you go from street address and you hit tab and it puts in the zip code field.
00:05:58.399 --> 00:06:01.120
And then you hit tab and it goes back to state.
00:06:01.279 --> 00:06:04.720
And you hit tab and it goes to street address too, or like it, it's all over the place.
00:06:04.800 --> 00:06:06.399
And you're like, what's going on here?
00:06:06.639 --> 00:06:08.879
That's not behaving as expected.
00:06:09.120 --> 00:06:12.959
Checking tab order is not necessarily something that developers often do.
00:06:13.199 --> 00:06:15.040
We say, yeah, they're all there.
00:06:15.439 --> 00:06:20.480
But the QA person goes, yes, but it's not behaving as expected.
00:06:20.800 --> 00:06:30.639
And then with this, they're representing the user when it comes to performance, where they go, yeah, it all works, but it takes five seconds to load a new page and they need to move.
00:06:30.879 --> 00:06:37.279
I've worked with people who have worked on a heads-down program, I call them, where they're not using their mouse.
00:06:37.439 --> 00:06:41.199
They're just putting as much information in as possible.
00:06:41.360 --> 00:06:51.759
They're just taking the data from paper and putting it in the computer, or they're filling out information as fast as possible, and they want to make sure their system
doesn't hold them back.
00:06:52.160 --> 00:06:56.560
And I've built systems where they held them back, and they're like, you're killing me.
00:06:56.879 --> 00:07:03.040
Because my job is dependent on how fast I do things, and your software is making me go slower.
00:07:03.279 --> 00:07:04.079
That's a problem.
00:07:04.319 --> 00:07:06.560
QAs have to step in and say, hey, you know what?
00:07:06.639 --> 00:07:08.160
No, this is not performant.
00:07:08.240 --> 00:07:10.959
This is not doing the right thing for the user.
00:07:11.040 --> 00:07:15.040
This is not the representing the user and saying, hey, they need better.
00:07:15.600 --> 00:07:17.199
So that's category number three.
00:07:17.360 --> 00:07:20.560
Category number four is they improve the process.
00:07:20.879 --> 00:07:34.720
So the process of getting the requirements to the developers, getting the requirements turned into code, getting the code tested, and getting the code back out to the user, that whole process can be improved by QA.
00:07:34.879 --> 00:07:36.879
That means they might create automated tests.
00:07:36.959 --> 00:07:40.319
It might mean they improve uh procedures and how you do things.
00:07:40.480 --> 00:07:52.720
That might mean they train the developers on where the bugs live or what the users actually want from their application so they can just do it the next time instead of having to have it come back from QA as a fail.
00:07:52.959 --> 00:07:56.639
And they build better test cases where they say, hey, you know what?
00:07:56.800 --> 00:08:01.680
There's some things that I've seen in when the users are using these things that we hadn't accounted for.
00:08:01.839 --> 00:08:03.360
And let's let's account for those things.
00:08:03.519 --> 00:08:06.240
So QA does a lot of great work.
00:08:06.639 --> 00:08:15.040
And there's a there's a difference between working on software and working on good software, right?
00:08:15.120 --> 00:08:19.839
There's a difference between saying, hey, it works and it works well.
00:08:20.079 --> 00:08:24.240
And QA is often the group that brings out that difference.
00:08:24.959 --> 00:08:28.480
So let's ask the question here: why can't AI do this?
00:08:28.720 --> 00:08:31.759
Because it seems like that's a role for AI, right?
00:08:32.159 --> 00:08:36.480
No, because AI doesn't actually fully test its own code.
00:08:36.720 --> 00:08:41.600
You might see, you know, AI writes code and goes, oh, I've also written 150 tests.
00:08:41.840 --> 00:08:47.440
Yeah, but those tests are written by the same person who created the code in the first place.
00:08:47.679 --> 00:08:54.799
They I'll often find the tests are really bad because they have the same assumptions as the code does.
00:08:54.960 --> 00:08:59.120
And so they're not actually testing that the functionality works the way it should.
00:08:59.279 --> 00:09:02.799
They're testing the same assumptions they had that were incorrect.
00:09:03.120 --> 00:09:09.840
So that's a problem, but it doesn't even understand all the code.
00:09:10.000 --> 00:09:17.279
And so it doesn't understand the greater context because it doesn't even have enough context window to put the entire code base in.
00:09:17.360 --> 00:09:20.639
And so what it does instead is it makes assumptions.
00:09:21.440 --> 00:09:25.679
And we all know that assumptions aren't good when it comes to code.
00:09:26.080 --> 00:09:29.039
Number two, AI only understands what you tell it.
00:09:29.279 --> 00:09:33.039
And even then, not necessarily all what you tell it.
00:09:33.279 --> 00:09:37.360
So when it comes to requirements, somebody has to gather those.
00:09:37.519 --> 00:09:41.039
And the user saying, here's my requirements, isn't gonna be good enough.
00:09:41.200 --> 00:09:44.559
And the developer saying, Well, I'm gonna give it better requirements.
00:09:44.879 --> 00:09:49.440
Unless you're good at QA, you're probably not gonna give it great instructions either.
00:09:49.519 --> 00:09:51.840
You'll get better instructions, much better instructions.
00:09:52.159 --> 00:10:06.720
But there is something to understanding fully what the user actually wants, how it actually needs to work, not just what they say, and then translate that into something that can be easier to understand as a developer.
00:10:07.039 --> 00:10:09.039
That's just something that AI can't do.
00:10:09.279 --> 00:10:12.000
Also, AI does not represent the user.
00:10:12.320 --> 00:10:19.039
It doesn't understand the user, it doesn't understand where they're coming from, it doesn't empathize with how they've done the work.
00:10:19.120 --> 00:10:20.720
It hasn't actually done the job.
00:10:20.879 --> 00:10:23.759
It hasn't learned because AIs don't learn.
00:10:24.000 --> 00:10:27.200
And so, yeah, even the memory files, not good enough.
00:10:27.519 --> 00:10:33.759
So it doesn't represent the user to go, hey, this needs to be more performant because this user does it things this way.
00:10:33.919 --> 00:10:40.399
It doesn't know about that unless you told it, which again comes back to it doesn't understand anything you don't tell it.
00:10:40.559 --> 00:10:45.360
And number four, AI isn't good at performing or improving procedures.
00:10:45.519 --> 00:10:53.039
Yes, if you push it and ask it and work with it, it can give you better procedures sometimes if it actually understands the problem.
00:10:53.200 --> 00:11:03.840
But more often than not, it's basically you like frog marching it until it gets to the point where it like gives you back what you were asking for in the first place.
00:11:04.000 --> 00:11:04.320
Right.
00:11:04.559 --> 00:11:07.440
So it's not good at improving procedures.
00:11:07.759 --> 00:11:09.840
So you need QA.
00:11:10.000 --> 00:11:23.440
And as a developer, if you haven't worked with a good QA department or you don't have access to one, I would encourage you to work on building up your own skills in this area because this is going to make you a better developer.
00:11:23.600 --> 00:11:28.720
The more you understand the QA role, the better you get at it, the better you will be as a developer.
00:11:28.879 --> 00:11:34.480
And which is also why I encourage new developers who are struggling to find development roles to look at the QA roles.
00:11:34.799 --> 00:11:38.559
They aren't the same and they often don't include development.
00:11:38.639 --> 00:11:41.919
So it's not like you're just, you know, developer and waiting necessarily.
00:11:42.080 --> 00:11:42.879
They can be.
00:11:43.200 --> 00:11:49.519
But what it does do is it gives you the skills and experience you're gonna need to be a better developer when your time comes.
00:11:50.559 --> 00:11:56.399
The role of a QA developer is something that is badly needed in a lot of organizations.
00:11:56.559 --> 00:12:00.879
I see a lot of companies that are kind of skipping that because who needs quality anymore, right?
00:12:01.279 --> 00:12:02.159
We have quantity.
00:12:02.320 --> 00:12:03.919
Quantity is not the solution.
00:12:04.159 --> 00:12:05.360
Quality is a solution.
00:12:05.519 --> 00:12:07.519
That's where you get the sticking power of an application.
00:12:07.679 --> 00:12:11.440
That's where things go from they work to they work well.
00:12:12.000 --> 00:12:16.080
So if you have your QA people in your team, give them a hug.
00:12:16.240 --> 00:12:17.120
They're awesome.
00:12:17.360 --> 00:12:19.039
Um learn from them.
00:12:19.200 --> 00:12:21.519
And if you don't, learn how to be them.
00:12:21.600 --> 00:12:23.200
And even if you do, learn from them.
00:12:23.360 --> 00:12:36.480
Learn how to be a better developer because you learn from your QA people and get better at understanding what they do, why they do it, and how you can incorporate some of those same techniques into your development experience.
00:12:36.559 --> 00:12:36.879
Okay.
00:12:37.600 --> 00:12:38.879
QA is important.
00:12:39.120 --> 00:12:40.639
AI can't replace it.
00:12:40.879 --> 00:12:46.000
It is a necessary role to put out good software, not just working software.
00:12:46.080 --> 00:12:46.559
All right.
00:12:46.720 --> 00:12:47.519
Thanks for listening.
00:12:47.759 --> 00:12:49.679
As always, I am Tim Corey.