Software QA Tools and Methods

Name: Software QA Tools and Methods
Author: Andrew Levin

Learn different techniques for testing your software

Preview the first lesson free — get full access to all 8 lessons.

Course: On-Demand

Hello, everyone. Welcome to Knowledge City's course, software, QA tools, and methods. In this module, we're gonna look at different testing techniques you can use to see if your program is working correctly. Techniques that could be considered white box techniques, black box techniques. In this lesson, we're gonna look at one called statement coverage. We're gonna look at other techniques in future lessons, such as decision tables and boundary testing. But in this lesson, we'll look at statement coverage, which is probably one of the simplest to do. What exactly is statement coverage? Simply put, does every line of code, does every statement get to run at least once? Does this program hit it at least once? Now I'm not talking about comments. Comments are lines in the code that only other programmers see. The users should never see a comment line. So I'm not talking about comments. I'm talking about actual code that is supposed to do something in your program. How can that happen? Why would code be in there that never gets run? Well, it could be something linked to a branching issue, which we're gonna talk about in a future lesson. But one of the most common reasons is because you may have removed something and didn't remove everything. So what's the big deal? So what if a line or two doesn't get run? Well, couple of reasons. If it never gets run, why is it in there? Number one, and number two, having lines in there that never get run, that causes the program to be bigger. It could cause it to slow down. You don't know what kind of issues you'll hit in the future. So obviously the goal is 100% usage. So let's see an example. Okay, we have a program that I made. It's, we'll see it later. This is just one screenshot where we're going to remove this button. The program doesn't need that button anymore. When you remove the button, this button, unfortunately or fortunately, called a subroutine up here called AccOMNIToAzure. So a statement review would show me, hey, nobody ever calls this anymore. So when we got rid of the button, we should have gotten rid of the subroutine because it's never going to be hit. If nobody ever calls this subroutine, it never gets hit. So a very simple way to check if you have any code that never gets hit, is to look at a list of all your subroutines that you created, and simply do a search like you would through a Word document. Look for those words and see if you see any line that says anything along the lines of, call AccOMNIToAzure. Because if you don't find it anywhere, it's never getting hit. Okay, so this lesson talked about statement coverage. In future lessons, you'll see other types of testing you can do. Thanks for coming, and I'll see you next time.

Beginner Provider : Andrew Levin 8 Lessons · 30m in Arabic, German, English, Spanish, French, Portuguese, Urdu, Chinese

Course Description

In this chapter you will learn about different testing techniques you can apply to your code in order to check for errors and proper usage. You will explore different Black Box and White Box testing techniques, what they are used for, when to use them, and how to use them with actual working software samples.

What You'll Learn

Differentiate Black Box and White Box testing techniques and their test cases
Apply statement coverage and branch coverage to check code paths for errors
Use boundary testing and equivalence testing to design effective test cases
Build decision table and state transition tests for varied conditions
Determine how, when, and why to apply each testing technique based on what you are checking
Distinguish functional from non-functional testing and scale up the testing ladder

Key Takeaways

Different testing techniques exist to check code for errors and proper usage, including Black Box and White Box approaches.
Choosing a testing technique depends on what you are trying to check for errors, so the course covers when and why to use each one.
White Box techniques such as statement coverage and branch coverage examine the internal paths of code.
Black Box techniques such as boundary testing, equivalence testing, decision table testing, and state transition testing focus on inputs and expected behavior.
The course distinguishes functional from non-functional testing and demonstrates techniques with actual working software samples.

Frequently Asked Questions

What does this course cover?

It covers different testing techniques you can apply to your code to check for errors and proper usage, exploring Black Box and White Box techniques including statement coverage, branch coverage, boundary testing, equivalence testing, decision table testing, state transition testing, and functional and non-functional testing.

What is the difference between the testing techniques taught here?

The course teaches the differences between testing techniques such as Black Box and White Box test cases, and explains how, when, and why to use each based on what you are trying to check for errors.

What skills will I gain from this course?

You will build skills in Black-Box Testing, White-Box Testing, Gray Box Testing, Code Testing, Software Testing, and using Test Tools.

Does the course use real examples?

Yes, it shows how to use the different testing techniques with actual working software samples.