QA StepsLog in

What is software testing?

Software testing is checking software, and the documents around it, to find defects and judge its quality. At its simplest, you compare what the software does with what someone expected it to do, and you look for the differences on purpose, before a customer runs into them. Testing is important because software that does not work correctly costs money, time and reputation, and in some systems it can hurt people. A software tester finds out what changed, decides what to check, checks it, and reports what was found so that it can be fixed.

1 comparison
what it does vs what it should do
4 kinds of work
find, choose, check, report
2 ways to test
by reading and by running
Arti, the QA Steps tutor, in a scene for the article "What is software testing?"
The same topic as a short video lesson on the QA Steps YouTube channel.

Testing is a comparison

Shelf is the practice shop the author's courses use. Look at the cart below. Two Steel kettle 1.7 l at USD 24.00 each make USD 48.00. The coupon SAVE25 takes USD 25.00 off. The total says USD 0.00.

Before your eyes reached the total, you already knew what it should be: 48.00 minus 25.00 is 23.00. That number in your head is an expectation. The screen shows something else, and the gap between the two is a possible defect. Testing is the work of finding gaps like this one before customers do: you build that cart yourself, on purpose, and compare.

The expectation does not come from taste. It comes from a source: the coupon rules, the ticket, what any shop customer would assume. The guide on expected and actual results shows how to write it down and where to take it from.

One cart, one expectation
Cart
  Steel kettle 1.7 l     2 × USD 24.00
  Subtotal               USD 48.00
  Coupon SAVE25          −USD 50.00
  Shipping               Free
  Total                  USD 0.00

Expected: 48.00 − 25.00 = USD 23.00
Actual:   USD 0.00
Verdict:  different, a possible defect. Look closer and report it.
Diagram: Testing is a comparison

Why passing checks do not mean the software works

Many teams run automated checks and show the results on a dashboard. Suppose every tile is green and says "All checks passed" while the cart above shows USD 0.00. Nobody broke the dashboard.

An automated check answers only the question someone wrote into it. One check may ask whether the cart page opens. It does. Another may ask whether the coupon field accepts SAVE25. It does. If nobody wrote "Is the total right after a coupon?", nothing answers that question. Green means "these checks passed". It never means "the shop works".

Automation is useful, and many testers write it. But somebody has to decide what to ask, and that decision is testing too.

Why software testing is important

Many beginners think a bug is when the app crashes. Crashes are loud, and someone notices them within minutes. The cart above did not crash. It showed a calm, wrong number. Quiet defects like this are often the expensive ones: the shop loses money, the customer loses trust, and the team loses a day on refunds. In some software, such as medical or transport systems, a wrong number can hurt people.

Testing is also not limited to running the app. Reading a spec or reviewing code without running anything is called static testing; running the software is dynamic testing. Both find defects, and the earlier, the cheaper. A defect found in a sentence of the spec is fixed by changing the sentence. The same defect found after the feature is built means changing code, testing it again, and sometimes apologizing to customers.

What a software tester does

Here is a to-do list for one evening of testing in Shelf. Coupons changed today: there is a new code, SAVE25. Check the cart with one coupon, then with two. Check the product page of an item that is out of stock. Write up anything wrong before the morning release.

Read it again and you see four kinds of work, in this order:

  • Find out what changed

    A new coupon, a new button, a fixed bug. A change is the first place to look, because nobody has used it for real yet.

  • Decide what to check

    You cannot check everything, so you pick what matters most for this change and for the customer.

  • Check it

    Open the screen, do what a customer would do, and compare what you see with what you expected.

  • Report what you found

    Clearly enough that a developer can fix it without coming back to you with five questions.

Most of the job is thinking

A real day holds more around those four boxes: team meetings, reading requirements before any code exists (checking them, not writing them), writing your checks down, and a short report with a recommendation at the end. Not every team does all of it.

Notice how little of this is clicking. Clicking without an expectation finds nothing you can name. The job needs attention to detail, curiosity, and a calm way of saying uncomfortable things. Testers often bring bad news, and good ones report it about the product, never about a person. "The total shows USD 0.00 after SAVE25 on a USD 48.00 cart" helps the team. "Someone broke coupons again" starts an argument and fixes nothing.

You may have heard that testing is the easy way into IT. It is a profession with its own knowledge and skills, and the theory behind it is what most first-job interviews ask about.

Where to learn this

Questions and answers

What is software testing in simple words?

Comparing what a program does with what it should do, and looking for the differences on purpose. If a cart of USD 48.00 with a USD 25.00 coupon shows a total of USD 0.00, testing is how you find that before a customer does.

Why is software testing important?

Because software that does not work correctly costs money, time and reputation, and in medical or transport systems it can hurt people. Many defects do not crash anything. They show a wrong number or a wrong label, and only someone who knows what to expect will notice.

What does a software tester do?

Finds out what changed in the product, decides what to check, checks it against an expectation, and reports what is wrong so a developer can fix it. Around that: reading requirements, writing checks down, team meetings, and short reports.

Is software testing just clicking around?

No. Clicking without an expectation finds nothing you can name. Most of the work is reading, asking, choosing what to check, and writing clearly.

Is testing the same as debugging?

No. Testing finds failures and defects. Debugging finds, analyzes and removes the cause of a failure, and is usually a developer's work.

Can you test software without running it?

Yes. Reading a spec or reviewing code is static testing, and it finds defects before they are built. Running the software and comparing results is dynamic testing. Testers do both.

More guides

See the first course

The full outline of every course is available: you can see each lesson before you start.

All courses

Cookies keep you signed in. With your OK, one more remembers which link brought you here. Learn more