Scribd
Upload
64 views4 pages

Project Testing: 9.1 Description

The document discusses different types and levels of software testing. It describes unit testing, integration testing, functional testing, structural/white-box testing, and system testing. Unit testing tests individual code units in isolation before integration. Integration testing checks for proper interaction between integrated units. Functional testing focuses on validating required functions without considering internal structure. Structural testing evaluates internal paths and logic. System testing ensures the full application meets requirements as a whole. The project implements these testing levels to verify correct functionality and integration of all website pages and components.

Uploaded by

indu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
64 views4 pages

Project Testing: 9.1 Description

The document discusses different types and levels of software testing. It describes unit testing, integration testing, functional testing, structural/white-box testing, and system testing. Unit testing tests individual code units in isolation before integration. Integration testing checks for proper interaction between integrated units. Functional testing focuses on validating required functions without considering internal structure. Structural testing evaluates internal paths and logic. System testing ensures the full application meets requirements as a whole. The project implements these testing levels to verify correct functionality and integration of all website pages and components.

Uploaded by

indu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

CHAPTER 9

PROJECT TESTING

9.1 DESCRIPTION

The software engineering process can be viewed as a spiral. Initially system


engineering defines the role of software and leads to software requirement analysis
where the information domain, functions, behavior, performance, constraints and
validation criteria for software are established. Moving inward along the spiral, we
come to design and finally to coding. To develop computer software we spiral in
along streamlines that decrease the level of abstraction on each turn.
A strategy for software testing may also be viewed in the context of the spiral. Unit
testing begins at the vertex of the spiral and concentrates on each unit of the software
as implemented in source code. Testing progress by moving outward along the spiral
to integration testing , where the focus is on the design and the construction of the
software architecture. Talking another turn on outward on the spiral we encounter
validation testing where requirements established as part of software requirements
analysis are validated against the software that has been constructed. Finally we arrive
at system testing, where the software and other system elements are tested as a whole.

Fig.9.1 Process of Testing


9.2 FUNCTIONAL TESTING

Functional testing is a quality assurance (QA) process and a type of black box testing
that bases its test cases on the specifications of the software component under test.
Functions are tested by feeding them input and examining the output, and internal
program structure is rarely considered (not like in white-box testing).Functional
Testing usually describes what the system does. Functional testing typically involves
five steps:
The identification of functions that the software is expected to perform
The creation of input data based on the function's specifications
The determination of output based on the function's specifications
The execution of the test case
The comparison of actual and expected outputs.

Black-box testing is a method of software testing that examines the functionality of an


application (e.g. what the software does) without peering into its internal structures or
workings (see white-box testing).This method of test can be applied to virtually every
level of software testing: unit, integration, system and acceptance. It typically
comprises most if not all higher level testing. Black box testing tends to find different
kinds of errors than white box testing.

1. Missing functions
2. Usability problems
3. Performance problems
4. Concurrency and timing errors
5. Initialization and termination error

9.3 STRUCTURAL TESTING

White-box testing (also known as clear box testing, glass box testing, transparent box
testing, and structural testing) is a method of testing software that tests internal
structures or workings of an application, as opposed to its functionality (i.e. black-box
testing). In white-box testing an internal perspective of the system, as well as
programming skills, are used to design test cases. The tester chooses inputs to exercise
paths through the code and determine the appropriate outputs. This is analogous to
testing nodes in a circuit, e.g.in circuit testing (ICT). While white-box testing can be
applied at the unit, integration and system levels of the software testing process, it is
usually done at the unit level. It can test paths within a unit, paths between units
during integration, and between subsystems during a systemlevel test. Though this
method of test design can uncover many errors or problems, it might not detect
unimplemented parts of the specification or missing requirements. White-box test
design techniques include:

- Control flow testing


- Data flow testing
- Branch testing
- Path testing
- Statement coverage
- Decision coverage

9.4 LEVELS

9.4.1 Unit Testing:

White-box testing is done during unit testing to ensure that the code is working as
intended, before any integration happens with previously tested code. White-box
testing during unit testing catches any defects early on and aids in any defects that
happen later on after the code is integrated with the rest of the application and
therefore prevents any type of errors later on.

In this project, unit testing is implemented as every single page of the website is
executed and tested whether it is working properly or not.

9.4.2 Integration Testing:

White-box testing at this level is written to test the interactions of each interface with
each other. The Unit level testing made sure that each code was tested and working
accordingly in an isolated environment and integration examines the correctness of
the behavior in an open environment through the use of white-box testing for any
interactions of interfaces that are known to the programmer.

In this project, integration testing is implemented as we connected web pages and


checked whether the pages are properly connected or not.

9.4.3 System Testing:

System testing is important because of the following reasons:

System testing is the first step in the Software Development Life Cycle, where
the application is tested as a whole.
The application is tested thoroughly to verify that it meets the functional and
technical specifications.
The application is tested in an environment that is very close to the production
environment where the application will be deployed.
System testing enables us to test, verify, and validate both the business
requirements as well as the application architecture.
In our project, system testing is implemented as all the web pages are created and
connected then tested whether it works properly or not.

9.4.4 Project Testing:

When we completed Designing and coding of the projects, we had moved to project
testing phase. Now our project is ready for testing. What we have done in this phase is
that, crosschecking of links and sequence of page, also we checked that whether it is
accessible in browser history or not. Likewise proper website use to respond, this
website is website is responding or not on the similar attributes.
In this project, project testing is implemented after the completion of the project.
Testing is started by running index.html page and checked whether it meets all the
requirements of the use and working properly or not.

You might also like