Different Level Of Testing

-
There are four levels of testing :

  1. Unit Testing
  2. Integration Testing     
  3. System Testing
  4. User Acceptance Testing

1.Unit Testing: Unit testing is the level of the software testing process where an individual unit of software is tested. Unit testing searches for defects in and verifies the functioning of software modules, programs, objects, classes, etc. Unit testing occurs with access to the code being tested and with the support of the development environment, such as a unit test framework or debugging tools. Unit testing is done by the developer. The purpose is to validate that each unit of the software performs as designed. A unit is the smallest testable part of any software. Approach for using the unit Testing: 1.White-box testing 2.Black box testing
Benefits: 1. Unit testing increases confidence in changing/ maintaining code. 2. Codes are more reusable.
3. In order to make unit testing possible, codes need to be modular. This means that codes are easier to reuse. 4. The cost of fixing a defect detected during unit testing is lesser in comparison to that of defects detected at higher levels. 5. Debugging is easy.


2. Integration Testing: Integration testing is a level of the software testing process where individual units are combined and tested as a group. integration Testing focuses on checking data communication amongst these modules. Integration Test Case differs from other test cases in the sense it focuses mainly on the interfaces & flow of data between the modules. Strategies of Integration Testing:
1.Top-down testing
2.Bottom-up testing 3.Big bang Top-down Testing: In this approach, testing is done by joining two or more modules that are logically related. Then the other related modules are added and tested for the proper functioning. This process is carried out by using dummy programs called Stubs.
Bottom-up Testing: In the bottom-up strategy, each module at lower levels is tested with higher modules until all modules are tested. It takes the help of Drivers for testing.

This process is carried out by using dummy programs called Drivers.


Big bang Testing: Here all component are integrated together at once, and then tested. Convenient for small systems.

3. System Testing: In system testing the functionalities of the system are tested from an end-to-end perspective. System testing is usually carried out by a team that is independent of the development team in order to measure the quality of the system unbiased. It includes both functional and non-functional testing. System Testing is the testing of a complete and fully integrated software product. Testing is done by a professional testing agent on the completed software product before it is introduced to the market.


4.User Acceptance Testing: User acceptance testing is the last phase of the software testing process. During User acceptance testing, actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications.
This testing happens in the final phase of testing before moving the software application to the Market or Production environment.

 There are two types of user acceptance testing :
1.Alpha testing
2.Beta testing

 Alpha Testing: Alpha testing is a type of user acceptance testing performed to identify all possible issues before releasing the product.it is done only production environment.
Beta Testing: Beta Testing of a product is performed by real users of the software application in a real environment.it is also known as field testing.





Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

URL and COOKIES

-
Uniform Resource Locator (URL):    URL is an acronym for Uniform Resource Locator and is a reference (an address) to a resource on the Internet. URLs occur most commonly to reference web pages (Http) but are also used for file transfer (FTP), email (mailto), database access (JDBC), and many other applications.    A URL has two main components:    Protocol identifier: ​ For the URL http://example.com, the protocol identifier is Http.   Resource name:​ For the URL http://example.com, the resource name is example.com.    The resource name is the complete address to the resource. The format of the resource name depends entirely on the protocol used, but for many protocols, including HTTP, the resource name contains one or more of the following Components:   Host Name:​ The name of the machine on which the resource lives.  Filename: ​The pathname to the file on the machine.  Port Number: ​ The port number to ...
Read more