May 2019
Intermediate to advanced
456 pages
14h 27m
English
book
Improving Product Reliability and Software Quality, 2nd Edition
by Mark A. Levin, Ted T. Kalal, Jonathan Rodin
Content preview from Improving Product Reliability and Software Quality, 2nd Edition
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
22Software Testing and Debugging
Obviously, software needs to be tested prior to releasing it. There are several stages of testing that are executed sequentially to make for the most effective defect detection. First developers test their code, then it gets handed off to software quality assurance (SQA) to continue testing. Developer testing consists of unit tests and integration tests. SQA testing focuses on system testing. Unit tests exercise individual components in isolation. Integration testing checks the interaction between modules in a controlled manner. System testing exercises the entire software package. Testing should be done in the following order:
where each step is successfully concluded before the subsequent testing step is begun. Testing in this order is significantly more productive than attempting to run these tests in a different sequence. When individual components are tested first (during unit test) then the subsequent testing can focus on finding integration or system defects with the assurance that individual modules are relatively robust. If all the software is tested at once, it becomes very difficult to locate the root cause of a defect. Lots of time is spent trying to determine where a defect is located. This causes significant loss to productivity.
Details about the different types of testing can be found in the following sections.
22.1 Unit Tests ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.