Images Browser Compatibility Testing

Browser Compatibility Testing:

      Browser compatibility testing is defined as this requires that the web applications are tested on different web browsers, to ensure that the application is defect free.

     The goal of browser compatibility testing is to ensure that the site submit without error on the target web browsers. Some minor differences are expected from browser to browser, or within different versions of the same browser.

      Users typically view your website using a browser. Each browser interprets the code page of the website in a slightly different way. This means that your site visitors can look different depending on the browser used.

     Once you've designed your website, you should control their display and functionality in different browsers to make sure that visitors can use the service for which you worked so hard. In theory, it is preferable to start testing on the development process as soon as possible. Different browsers (and different versions of the same browser) can display your site differently.

Images Compatibility Testing

Compatibility testing:

      Compatibility testing is a type of software testing used to ensure compatibility of the system/application/website built with various other objects such as other web browsers, hardware platforms, users (in case if it’s very specific type of requirement, such as a user who speaks and can read only a particular language), operating systems etc. This type of testing helps find out how well a system performs in a particular environment that includes hardware, network, operating system and other software etc.

      It tests whether the application or the software product built is compatible with the hardware, operating system, database or other system software or not.

It is a type of non-functional testing.

Compatibility testing, part of software non-functional tests, is testing conducted on the application to evaluate the application's compatibility with the computing environment.

Images Boundary Value Analysis

Boundary value analysis:

Boundary value analysis (BVA) is based on testing at the boundaries between partitions.

     

      ‘Boundary value analysis’ testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain.

     

      Boundary value analysis is a next part of Equivalence partitioning for designing test cases where test cases are selected at the edges of the equivalence classes.

Example:

As an example, consider a printer that has an input option of the number of copies to be made, from 1 to 99. To apply boundary value analysis, we will take the minimum and maximum (boundary) values from the valid partition (1 and 99 in this case) together with the first or last value respectively in each of the invalid partitions adjacent to the valid partition (0 and 100 in this case). In this example we would have three equivalence partitioning tests (one from each of the three partitions) and four boundary value tests.

Images Acceptance Testing

After the system test has corrected all or most defects, the system will be delivered to the user or customer for acceptance testing.

Acceptance testing is basically done by the user or customer although other stakeholders 

may be involved as well.

The goal of acceptance testing is to establish confidence in the system. 

Acceptance Testing is a level of the software testing process where a system is tested for acceptability.

The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery. 

Images Alpha & Beta Testing

What is Alpha Testing ?

Alpha testing is a type of acceptance testing; performed to identify all possible issues/bugs before releasing the product to everyday users or public.  The focus of this testing is to simulate real users by using blackbox and whitebox techniques. The aim is to carry out the tasks that a typical user might perform. Alpha testing is carried out in a lab environment and usually the testers are internal employees of the organization. To put it as simple as possible, this kind of testing is called alpha only because it is done early on, near the end of the development of the software, and before beta testing.

Read More >>