Black box testing: Black box testing is not based on any knowledge of internal design or code. This test is based mainly on requirements and functionality.
White box testing: White box testing is mainly based on information of the internal logic of an application’s code.
Tests are base on coverage of code statements, branches, paths, conditions.
Software Testing Services
Unit testing: This test is mainly performed by the programmer not by the tester. This is the smallest compliable component. This unit is tested in isolation by the help of drivers or stubs.
Incremental integration testing: Incremental integration testing is a process to perform continuous testing of an application if new functionality is added. It needs that all the different feature of an application’s functionality be independent sufficient to perform the task independently before the entire parts of the program are finished, or that test drivers be developed as needed; complete through programmers or by testers.
Integration testing: Integration testing is the collective fraction of an application to determine that all the parts are functioning mutually and providing the result as expected. Each part may be code of modules, individual software development applications, client and server applications on a network, etc. This kind of testing is particularly pertinent to client/server and distributed systems.
Functional testing: Black-box testing intended to authenticate to functional needs of an application; this kind of testing must be performed by testers.
System testing: System testing is like Black-box testing which is based on the whole needs condition; covers the entire mutual parts of a system.
Offshore software development
End-to-end testing: Alike to system testing other than engage testing of the software development application in a situation which imitate real-world exercise, like interacting with a database, using network communications, or applications, interacting with other hardware, or systems if appropriate. Still the dealings performed mimic the end users practice of the application by software development .
Sanity testing: Sanity testing is normally an early testing attempt to decide if a new software version is carrying out well enough to accept it for a major testing effort.
Smoke testing: Smoke testing is a safe risk-free process of bluster smoke into parts of the sewer and drain lines to recognize sources of unwanted leaks and sources of sewer odors.
Regression testing: Testing of a previously established program or application following program alteration for extension or correction to make sure no new errors have been introduced. For this type of testing, software development automated testing tools is very much useful.
Acceptance testing: Final testing is to verify the end-user or customer specifications, or based on utilize by end-users/customers over a number of limited period of time.
Load testing: Load testing is to determine the maximum sustainable load of the system to mange with a specific time. Load is varied from a minimum (zero) to the maximum level the system can sustain with no running out of resources or having, transactions experience extreme delay.
