Dry Run Testing in Software Development

An error occurred trying to load this video.

Try refreshing the page, or contact customer support.

Coming up next: Deployment Phase in SDLC

You're on a roll. Keep up the good work!

Take Quiz Watch Next Lesson
Your next lesson will play in 10 seconds
  • 0:00 Software Development…
  • 1:20 Dry Run Testing
  • 2:38 Benefits of Dry Run Testing
  • 3:06 Lesson Summary
Save Save Save

Want to watch this again later?

Log in or sign up to add this lesson to a Custom Course.

Log in or Sign up

Speed Speed

Recommended Lessons and Courses for You

Lesson Transcript
Instructor: Lucinda Stanley

Lucinda has taught business and information technology and has a PhD in Education.

In this lesson, we will explore the dry run testing phase of the software development life cycle. We will consider the process and benefits of dry run testing.

Software Development Life Cycle

Have you ever bought a new piece of software and found yourself saying: ''There are so many bugs I can't even use this software!'' I hope not! But if you have, it's likely because the developer didn't take the time to do some dry run testing of the software before they made it available to users. Testing software is an important part of the software development life cycle.

The Software Development Life Cycle (SDLC) is a framework or process for tasks that need to be accomplished in developing software. The life cycle consists of five processes, including analyzing and planning, defining requirements, developing, testing, and deployment.

Software Development Life Cycle
Software Development Life Cycle

Testing actually may happen throughout the development process to find and fix problems. The formal testing phase happens after there has been a needs analysis (what is the purpose of the software), the specific requirements (what do we want it to do) are defined, and the software code is written, but before the software is released to the end user (deployment).

The two types of tests that may be performed are static and dynamic. Static testing is done before a prototype is developed. Dynamic testing is done with a working prototype of the software.

Dry Run Testing

Dry run testing is a static test and should be performed by the developer to mitigate the effects of a failure of the product - meaning before the end user gets the product and discovers it doesn't do what it says it will. In dry run testing, no hardware is used, but it is assumed that the programmer who is testing the code is aware of what each line of code is supposed to do and gives him or her the opportunity to make corrections to the code before it becomes an issue for the actual software. Basically, a dry run test consists of programmers manually reading their code line by line to find errors and fix them. This is a simple Visual Basic code page; a full software application code page would look much more involved.:

Visual Basic Code
Visual Basic Code

To unlock this lesson you must be a Study.com Member.
Create your account

Register to view this lesson

Are you a student or a teacher?

Unlock Your Education

See for yourself why 30 million people use Study.com

Become a Study.com member and start learning now.
Become a Member  Back
What teachers are saying about Study.com
Try it risk-free for 30 days

Earning College Credit

Did you know… We have over 200 college courses that prepare you to earn credit by exam that is accepted by over 1,500 colleges and universities. You can test out of the first two years of college and save thousands off your degree. Anyone can earn credit-by-exam regardless of age or education level.

To learn more, visit our Earning Credit Page

Transferring credit to the school of your choice

Not sure what college you want to attend yet? Study.com has thousands of articles about every imaginable degree, area of study and career path that can help you find the school that's right for you.

Create an account to start this course today
Try it risk-free for 30 days!
Create an account