Testing Internet-based applications is best tackled with a divideand- conquer approach. Fortunately, the architecture of Internet applications allows you to identify discrete areas to target testing.
(prHWY.com) August 10, 2012 - Edmond, OK -- Developing a testing strategy for
Internet-based applications requires a solid understanding of each of the hardware and software components that make up the application. As is critical to successful testing of standard applications, a specification document is needed to describe the expected functionality and performance of your Website. Without this document, you cannot design the appropriate tests.
You need to test components developed internally and those purchased from a third party. For the components developed in-house you should employ the tactics presented in earlier chapters. This includes creating unit/module tests and performing code reviews.
You should integrate the components into your system only after verifying that they meet the design specifications and functionality outlined in the specification document.
If you purchase components, then you need to develop a series of system tests to validate that the items perform correctly independently of your application. Do not rely on the vendor's quality-control program to detect errors in its components. Ideally, you should complete this task independently of your
application testing. Integrate these components only once you determine that they perform acceptably. Including a nonfunctional third-party component in your architecture makes it difficult to interpret test results and identify the source of errors. Generally, you will use black-box approaches for third-party components because you rarely have access to the component internals.
Testing
Internet-based applications is best tackled with a divideand- conquer approach. Fortunately, the architecture of Internet applications allows you to identify discrete areas to target testing. The below Figure provides a more detailed view of each tier.
Internet applications are considered three-tier client-server applications. Each tier, or layer, from below Figure is defined as follows:
* Presentation layer. The layer of an Internet application that provides the GUI (graphical user interface).
* Business Logic layer. The layer that models your business processes such as user authentication and transactions.
* Data Access layer. The layer that houses data used by the application or that is collected from the end user.
Each tier has its own characteristics that encourage test segmentation. Testing each tier independently allows you to more easily identify bugs and errors before complete
system testing begins. If you rely only on system testing, then you may have a difficult time locating the specific components that are creating the problem.
The below Table lists items that you should test in each tier. The list is not complete, but provides a starting point to develop your own testing criteria. In the remainder of this chapter we provide more details on how to test each tier.
Read More:
Software Testing Guide:
###