Due to the complex architecture of web systems, interface and compatibility issues may occur on several areas. The core components are web servers, application servers and database servers (and possibly mail servers). Web servers normally hosts HTML pages and other web services. Application severs typically contains objects such as programs, scripts, DLLs or third party products, that provide and extend functionality and effects for the web application.
Test the communication between the different servers by making transactions and view logfiles to verify the result. Depending on the configuration of the server side compatibility issues may occur depending on, for example, server hardware, server software or network connections. Database compatibility issues may occur depending on different database types (SQL, Oracle, Sybase etc.).
Issues to test:
- Verify that communication is done correctly, web server-application server, application server-database server and vice versa.
- Compatibility of server software, hardware, network connections
- Database compatibility (SQL, Oracle, Sybase etc.)
Client Side compatibility:
Platform
There are several different operating systems that are being used on the market today, and depending on the configuration of the user system, compatibility issues may occur. Different applications may work fine under certain operating systems, but fail under another. The following are the most commonly used:
Windows (95, 98, 2000, NT)
Unix (different sets)
Macintosh
Linux
Browsers
The browser is the most central component on the client side of the web. Browsers come in different brands and versions and have different support for Java, JavaScript, ActiveX, plugins or different HTML specifications. ActiveX, for example, is a Microsoft product and therefore designed for Internet Explorer, while JavaScript is produced by Netscape and Java by Sun. This substantiates the fact that compatibility problems commonly occur. Frames and Cascading style sheets may display differently on different browsers, or not at all. Different browsers also have different settings for e.g. security or Java support.
- Internet Explorer (3.X 4.X, 5.X)
- Netscape Navigator (3.X, 4.X, 6.X)
- AOL
- Browser settings (security settings, graphics, Java etc.)
- Frames and Cascade Style sheets
- Applets, ActiveX controls, DHTML, client side scripting
- HTML specifications
- Graphics
Settings, Preferences
Depending on settings and preferences of the client machine, web applications may behave differently. Try and vary the following:
- Screen resolution (check that text and graphic alignment still work, font are readable etc.)
- Colour depth (256, 16-bit, 32-bit)
Printing
Despite the paperless society the web was to introduce, printing is done more than ever. Verify that pages are printable with considerations on:
- Text and image alignment
- Colours of text, foreground and background
- Scalability to fit paper size
- Tables and borders
related post
UNIT TESTING PART ONE
UNIT TESTING PART TWO
UNIT TESTING PART THREE
GUI TESTING
WINDOWS COMPLIANCE GUI TESTING PART ONE
WINDOWS COMPLIANCE GUI TESTING PART TWO
WINDOWS COMPLIANCE GUI TESTING PART THREE
WINDOWS COMPLIANCE GUI TESTING PART FOUR VALIDATION TESTING
WINDOWS COMPLIANCE GUI TESTING PART FIVE CONDITION TESTING
WINDOWS COMPLIANCE GUI TESTING PART SIX GENERAL CONDITION TESTING
CONDITION TESTING
TESTING CONDITIONS PART ONE
TESTING CONDITIONS PART TWO
TESTING CONDITIONS PART THREE
TESTING CONDITIONS PART FOUR
SPECIFIC FIELD TESTING
USABILITY TESTING
INTEGRATION TESTING
INTEGRATION TESTING PART ONE
INTEGRATION TESTING PART TWO
INTEGRATION TESTING PART THREE
INTEGRATION TESTING PART FOUR
INTEGRATION TESTING PART FIVE
INTEGRATION TEST STANDARDS
INTEGRATION TEST STANDARDS PART TWO
No comments:
Post a Comment