The software engineering process

TESTING

Testing is the process of detecting errors. Testing plays a very important role in quality assurance and for ensuring the software reliability. The testing parameters can be used even in the maintenance mode. The system engineering has the role for software and lead to software development analysis where the information performance functions,constraints, behavior, domain and validation criteria for the software to be established. The underlying motivation of program testing is to affirm software quality with methods that can economically and effectively apply to both strategic to both large and small scale systems.

The software engineering process is to be viewed as a spiral process. The system engineering has the role for software and lead to software development analysis where the information performance functions,constraints, behavior, domain and validation criteria for the software to be established. Moving towards the inward of the spiral, we come into design and finally onto coding. In order to develop computer software we spiral through the streamlines of the decreased level of abstraction on each of turn.

A concept for software testing will also be viewed in the view of the spiral model. Unit testing starts at the edge of the spiral and on each unit of the software has processed in the source code. Testing starts by moving outward to the spiral to the integration testing, where the focussing in the design and the construction of the software architecture. Talking an other turn on outward on the spiral model we have to encounter the validation testing where requirements are established as an integral part of software requirements analysis stage and are validated against the software that has been constructing. Finally we will arrive at the system testing, where the software on other system items are tested on the whole.

criteria of Testing

The aim of testing is to show that a program works without showing errors. The main purpose of testing phase is to detect the errors that are present in the program. So, one should not start testing with the intent to show that a program works, but the intent should not be to show that a program doesn't work. Testing is the process of executing a program with the intent of finding errors and resolving bugs.

Testing Objectives

The objective of testing is to detect errors minimum effort and time. The following objectives must be met:

  • The aim of testing is to show that a program works without showing errors.
  • The main purpose of testing phase is to detect the errors that are present in the program.
  • One should not start testing with the intent to show that a program works
  • Testing plays a very important role in quality assurance and for ensuring the software reliability.
  • The underlying motivation of program testing is to affirm software quality with methods that can economically and effectively apply to both strategic to both large and small scale systems.

System Testing

The concept behind testing is to find errors. Test cases are developed with this in mind. A strategy employed for system testing is code testing.

Code Testing

This strategy examines the code of the program. To follow this method we need to developed some test data that is used to execute every instruction in the program and module i.e. every path is tested. Systems are not designed to test entire project at a time. They are tested as single systems. To ensure that the coding is perfect two types of testing is performed or for that matter is performed or that matter is performed or for that matter is performed on all systems.

Test is performed with realistic data of the client to demonstrate that the software is working correctly. Testing here is focused on external behavior of the system, the internal logic of program is not emphasized.

It is performed with realistic data of the client to demonstrate that the software is working satisfactorily. In the Generic code project testing is done to check whether the Creation of tables and respected data entry was working successfully or not.

Types of Testing

Unit Testing

Unit testing will focus on checking on the small units of software, that is the module. By using a detailed designs and the process trends in testing can be done to uncover errors in the boundary of the module. The module must achieve success in the unit test before they start the integration testing process.

Test is performed with realistic data of the client to demonstrate that the software is working correctly. Testing here is focused on external behavior of the system, the internal logic of program is not emphasized.

It is performed with realistic data of the client to demonstrate that the software is working satisfactorily. In the Generic code project testing is done to check whether the Creation of tables and respected data entry was working successfully or not.

In this project integrating all the modules forms the main system. When integrating all the modules we have checked whether the integration effects working of any of the services by giving different combinations of inputs with which the two services run perfectly before Integration.

Link Testing

Link testing does not test software but rather the integration of each module in system. The primary concern is the compatibility of each module. The Programmer tests where modules are designed with different parameters, length, type etc.

This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.

Integration Testing

After the unit testing we have to perform integration testing. The goal here is to see if modules can be integrated properly, the emphasis being on testing interfaces between modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.

Test is performed with realistic data of the client to demonstrate that the software is working correctly. Testing here is focused on external behavior of the system, the internal logic of program is not emphasized.

It is performed with realistic data of the client to demonstrate that the software is working satisfactorily. In the Generic code project testing is done to check whether the Creation of tables and respected data entry was working successfully or not.

In this project integrating all the modules forms the main system. When integrating all the modules we have checked whether the integration effects working of any of the services by giving different combinations of inputs with which the two services run perfectly before Integration.

System Testing

Here the entire software system is tested. The reference document for this process is the requirements document, and the goal is to see that its software requirements are met.

Test is performed with realistic data of the client to demonstrate that the software is working correctly. Testing here is focused on external behavior of the system, the internal logic of program is not emphasized.

It is performed with realistic data of the client to demonstrate that the software is working satisfactorily. In the Generic code project testing is done to check whether the Creation of tables and respected data entry was working successfully or not.

Acceptance Testing

Acceptance Test is performed with realistic data of the client to demonstrate that the software is working correctly. Testing here is focused on external behavior of the system, the internal logic of program is not emphasized.

It is performed with realistic data of the client to demonstrate that the software is working satisfactorily. In the Generic code project testing is done to check whether the Creation of tables and respected data entry was working successfully or not.

White Box Testing

This is a unit testing method where a unit shall be taken at a time and tested thoroughly at a statement level to find the maximum possible errors. I tested step wise every piece of code, taking care that every statement in the code is executed at least once. The white box testing is also called Glass Box Testing. I have generated a list of test cases, sample data. This is used to check all possible combinations of execution paths through the code at every module level.

This type of testing ensures that

  • The independent paths are to be executed at least once
  • The logical decisions are to be taken on their true or false sides
  • The loops are to be runned and debugged at boundaries and within the operational bounds
  • The internal data structures are exercised in order to assure the validity.

In order to follow the concept of the white box testing we have tested each form. we have to create an independently verify that Data flow is correct, The conditions are checked and checked till the validities, The loops are executed on their boundaries.

Black Box Testing

This testing method will consider the module as a single unit of notation and checks the unit as an interface and communication to other modules other than getting into details of statement level. Here the module shall be treated as a block box that shall take an input and generate output. Output for a given as a set of input combinations and are forwarded to other modules.

It is a test case design for method used in the functional requirement of the software. Black Box testing will help to find errors in the following categories:

  • Incorrect and missing function
  • Interface of errors
  • Errors in the data structure
  • Performance of error

Initialization and termination errors

TEST APPROACH

Testing can be done in two different ways:

  • Bottom up approach
  • Top down approach

Bottom up approach

Testing can be performed starting from smallest and lowest levelled modules and proceeded with one at a time. For each module in bottom up testing approach a short program shall execute the module and provide the needed data, so that the module is asked to perform the way it shall when embedded within the larger system. When bottom level module is tested the concentration turns to those on the next level that use the lower level ones they are tested individually and then linked with the previously examined lower level modules.

Top down approach

The type of testing startsin the upper level module. Since all the detailed activities usually performed at the lower level routines and are not provided when stubs are written. A stub is a module shell is normally called the upper level module and is to be reached properly shall return a message to the calling module indicating with proper interaction occurred. There is no attempt is made to verify the correctness of the lower level module

Criteria Satisfied by Test Cases

Test cases reduce the count that is greater than one , the additional test cases are designed much attractively in the archive for reasonable testing

Testing primarly focusses on the absence of class errors rather than errors specific to the test hand and sometimes even to greater extent.

TEST CASES

Test case for Login form:

When a user tries to login by submitting an incorrect ID or an incorrect Password then it generates an error message "NOT A VALID USER NAME".

TEST CASE 2:

Test case for User Registration form:

When a user enters user id to register and ID already exists, then this result in displaying error message is generated called "USER ID ALREADY EXISTS".

TEST CASE 3:

Test case for cart:

When a customer has an empty cart it generates a cart is empty message.

When a user wants to add a product to cart without logging into the system a message is genereated "Please login to purchase"

TEST CASE 4:

Validation cases:

The validation error is generated when the data field is not accepted fromm validation of the user.

Please be aware that the free essay that you were just reading was not written by us. This essay, and all of the others available to view on the website, were provided to us by students in exchange for services that we offer. This relationship helps our students to get an even better deal while also contributing to the biggest free essay resource in the UK!