Cross Browser Testing - Basics - Learner's Series - 2

When there is scope for BCT in your application, you might want to consider

• Features/ Functionalities that will be covered 
• User experience issues that might be faced
• When you would do BCT?
• Selecting the right or closest possible Browser/OS/Device Matrix
• Test cases that would be needed for BCT?
• Cross Browser Test Tools
• Execution Build Scope

BCT Scope - Functional Test Areas

From the Major areas of functional testing, variety of specific test scenarios can be reused or designed by combining one or more areas mentioned below for BCT.

E2E Scenario Testing

Testing that cover multiple activities connected end-to-end across various functionalities of an application.

User documentation

Some web applications have a Help guide which is part of the functionality explains about the ways to use the application, GUI etc, which might be necessary for Customer Satisfaction.

Data Management

Some web applications displays different types of data which might be very important(Exam results, Bank Account Transactions, Travel Reservations etc)

•        Input data that is processed by the application.
•        Output data that results from processing by the application.
•        Preset data that is supplied as part of the application, or otherwise built into it, such as databases, default values, etc and will be displayed as part of administration/configuration etc
•       Persistent data that is stored internally and expected to persist over multiple operations. This includes modes or states of the application, such as options settings, view modes, contents of documents, etc and displayed to the user.

Testability

Testing that covers the quality of Transaction/Error Logs (only if it is stored in Database and local disk), Error Messages, and All pop-up messages of an application.

User Management

Testing that covers the User Management – Creation, Updating (username, password, Profiles etc), removing users (if user management is not part of the E2E Scenarios testing) and is used by different user groups on a regular basis.

Configuration

Testing that covers the Administration pages, Application Configuration (User-level) etc of an application. This testing will be applicable only if the application has administration/different user levels as its features.

Page template testing

Testing that covers features from at least one web page from different web page templates of an application. This testing will be applicable only if the application has many page templates.

The above testing might cover the below combined with functionality

·         GUI functionality- Displaying and working of various GUI controls with Functionality

·         Client-side validations

Mandatory Fields which is needs to be entered while using an application. 

Example: - In Some web applications, the functionality might require the mandatory fields are Name, Country etc.  to be entered. When the data is missed, client side application itself will validate instead of the server on the correctness.

·         Effect of browser settings on functionality of the application

Required settings with respect to Cookies, JavaScript, and Security Levels will have an effect on the functionality of the application.

·         Level of Accessibility implementation( Administrator, Different User levels, Single Sign-On)

·         Browser’s ability to inter-operate with other software programs(PDF Reader, Office document(Microsoft, Open Office)