Scribd
Upload
94 views3 pages

Testing

The document discusses different types of software testing: system testing ensures the system works accurately before launch; unit testing checks for errors from improper inputs; integration testing combines modules and tests the full system; validation testing checks if the software meets user expectations; acceptance testing verifies the software functions as reasonably expected; white box testing checks all logical paths and decisions; and black box testing focuses on functional requirements without viewing internal structures.

Uploaded by

Tajudeen Taju
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
94 views3 pages

Testing

The document discusses different types of software testing: system testing ensures the system works accurately before launch; unit testing checks for errors from improper inputs; integration testing combines modules and tests the full system; validation testing checks if the software meets user expectations; acceptance testing verifies the software functions as reasonably expected; white box testing checks all logical paths and decisions; and black box testing focuses on functional requirements without viewing internal structures.

Uploaded by

Tajudeen Taju
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/ 3

SOFTWARE TESTING

A test case is an asset of data that the system will process as normal input. The strategies
that we have used in our project are,
SYSTEM TESTING
Testing is the stage of implementation of which aimed at ensuring that the system works
accurately and efficiently before live operation commences. Testing is vital to the success of the
system. System testing makes a logical assumption that if all the parts of the system are correct
the goal will be achieved. The candidates system subject to a variety of tests. Online response,
volume, stress, recovery, security and usability tests. A series of testing are performed for the
proposed system before the system is ready for user acceptance testing.

UNIT TESTING

The procedure level testing is made first. By giving improper inputs, the errors occurred
are noted and eliminated .Then the web form level is made.

INTEGRATION TESTING:

Testing is done for each module. After testing all the modules, the modules are integrated
and testing of the final system is done with the test data, specially designed to show that the
system will operate successfully in all its aspects conditions. Thus the system testing is a
confirmation that all its correct and an opportunity to show the user that the system works.

VALIDATION TESTING:

The final step involves validation testing which determines whether the software function
as the user expected. The end-user rather than the system developer conduct this test most
software developers as a process called “Alpha and Beta test” to uncover that only the end user
seems able to find. The compilation of the entire project is based on the full satisfaction of the
end users.
ACCEPTANCE TESTING:
Acceptance testing can be defined in many ways, but a simple definition is the succeeds
when the software functions in a manner that can be reasonable expected by the customer. After
the acceptance test has been conducted, one of the two possible conditions exists. This is to fine
whether the inputs are accepted by the database or other validations. For example accept only
numbers in the numeric field, date format data in the date field. Also the null check for the not
null fields. If any error occurs then show the error messages. The function of performance
characteristics to specification and is accepted. A deviation from specification is uncovered and a
deficiency list is created.

WHITE BOX TESTING

White box testing, sometimes called "Glass-box testing”. Using white box testing
methods, the following tests were made on the system,

 All independent paths with in a module have been exercised at least once.
 All logical decisions were checked for the true and false side of the values.
 All loops were executed to check their boundary values.
 Internal data-structure was tested for their validity.

BLACK BOX TESTING

Black box testing focuses on the functional requirements of the software. That is black
box testing enables the software engineer to drive a set of input conditions that will fully exercise
the requirements for a program. Black box testing is not an alternative for white box testing
techniques. Rather, it is a complementary approach that is likely to uncover different class of
errors. Black box testing attempts to find errors in the following categories:

 Interface errors.
 Performances in data structures or external database access.
 Performance errors.
 Initialization and termination errors.
Incorrect or missing functions.

You might also like