CST313 Week 2 Software Testing

docx

School

Ashford University *

*We aren’t endorsed by this school

Course

313

Subject

Industrial Engineering

Date

Dec 6, 2023

Type

docx

Pages

Uploaded by haydenherrig

Week 2: Software Testing Hayden Herrig University of Arizona Global Campus Prof. Amitava Karmaker October 11, 2023

Software Testing Testing is an important part of the software development process. Testing the software system being developed ensures that the system will function as the client intends to. If it is found in testing that the software will not function as intended, changes can be made to the system to address any errors or issues in the system to make sure in the end the system will serve its intended purpose correctly. There are several different levels of testing that are performed throughout the development process. The purpose of these different levels of testing is to break down the testing instead of running everything at once and having a pile of errors to sort through. There are two different ways to carry out these tests thorough either the top down or bottom-up methods. This means testing either starts at the highest level of abstraction and works its way down to the lowest level of abstraction (top down), or testing starts at the lowest level of abstraction and works up to the highest level of abstraction (bottom up). It is more common that both top down and bottom-up are used together for effective testing. The different levels of testing commonly used are component testing, integration testing, system testing, and acceptance testing. Component testing focuses on testing the individual pieces of the system that have been developed. Component testing is meant to test units of the system such as scripts and other software components (Spillner et al., 2014). This ensures the individual pieces that will come together to make up the entirety of the program work as intended. Component testing in the general v-model relates to module design meaning component test plans should be developed during module design. These tests are then executed to eliminate bugs at the unit level (GeeksforGeeks, 2023).

Integration testing is performed to ensure that when the units are linked together the combined units will function as intended. The aim of integration testing is to test the interfaces between the modules and expose any defects that may appear when the components are integrated and need to interact with each other (Awati, 2022). Integration testing in the general V-model is related to the architecture design phase. The next level of testing is system testing. After integration testing verifies all the components are functional system testing conducted. The purpose of system testing is to check that the integrated product meets the specified function and non-functional requirements (GeeksforGeeks, 2023). The system tests are used to run the entirety of the system in a setting as close to the intended system environment. System tests are also meant to verify system and user documentation such as manuals and training materials. System testing in the general V-model is related to system design. The last level of testing is user acceptance testing. This testing is performed in a user environment that resembles the production environment. User acceptance testing verifies that the delivered system meets the user’s requirements and is ready to be used in the real world (GeeksforGeeks, 2023). There are several different types of acceptance testing that are used, such as contract acceptance testing, user acceptance testing, operational acceptance testing, and field testing. These types of acceptance testing are used depending on the environment the system is intended to be used in. In the general-V model this acceptance testing is related to requirements analysis. This is the final level of testing used to verify the system meets the requirements.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

References: Awati, R. (2022). integration testing or integration and testing (I&T). Software Quality. https://www.techtarget.com/searchsoftwarequality/definition/integration-testing GeeksforGeeks. (2023). Software Engineering SDLC V Model. GeeksforGeeks. https://www.geeksforgeeks.org/software-engineering-sdlc-v-model/ Spillner, A., Linz, T., & Schaefer, H. (2014). Software testing foundations: A study guide for the certified tester exam (4th ed.). Rocky Nook.

CST313 Week 2 Software Testing

Related Documents