Within the Software Development Lifecycle, it has a major step that takes a decent amount to do is Software testing. The purpose of software testing is that the program has no problems and meets the requirements set by the customer. Software development is divided into two different types: verification and validation. As noted before, verification is a step that has programmers checking if the software is doing as the customer intended. In the same vein, the validation step is just programmers testing if the software meets the customer’s requirements. For example a website wants to add a new feature to handle an increase of daily users on the platform.
Moving on, there are multiple different types of testing programmers use to validate and verify if the program is working as intended. There is automation testing, and manual testing. They then divide into smaller more specific tests that will focus on certain aspects of the program. As mentioned earlier, automation testing is when programmers write test scripts with or without software and can run the tests repeatedly. While manual testing is a method of testing that has a programmer write tests that will check on different sections of the program.
Within software testing there are different levels of testing. They are called unit testing, integration testing, system testing, acceptance testing.
Unit Testing
- It is a testing that checks every component or software
- It is to make sure the hardware or software that could be used by the programmers
Integration Testing
- It checks two or more modules which are tested are then put in the program or hardware
- To make sure the components and interface are working as intended
System Testing
- Is a test that verifies the software itself
- Also it checks the system elements
- If the program meets the requirements of the system
Acceptance Testing
- Validates if the program meets the customer’s expectation
- If the customer can work correctly on a user’s device
These different types of testing are used to prevent issues down the line. So that programmers can find potential bugs, improve quality of the program, improve user experience, testing for scalability, also to save time and money. In order to save money and time because it takes a lot of employees to solve problems with a program that could have been used to make a new product. A business wants a program to work and be improved over time.
From the blog CS@Worcester – Site Title by Ben Santos and used with permission of the author. All other rights reserved by the author.
