Page 121 - SOFTWARE TESTING & QUALITY ASSURANCE

Software Testing and Quality Assurance

When you are creating a new account registration, the data entered for the
phone number (mobile) should consist of ten (10) digits.

13. Cookies: If your Web site includes cookies, you need to check them also. When using cookies for
storing login information, make sure the cookies work and that the information is encrypted in the
cookie file. When using cookies for storing statistical data, verify that the totals are counted
properly. Also, ensure that those cookies are encrypted, so that they cannot be edited or modified.
14. Application Specific Functional Requirements: When testing a Web site, you need to verify the
application-specific functional requirements, before the user uses it.

While testing a Web site for a shopping center, test whether you can place an
order, change an order, cancel an order, enquire the status of the order, change
shipping information before an order is shipped, and pay online. You need to
ensure that a user can do what is advertised on the Web site.

15. Server Side Interface: Many a times, you may provide links which call external servers for
additional data, verification of data, or fulfillment of orders. Therefore, you need to perform the
server side interface test as well.
16. Server Interface: Test whether the browser is interfacing properly with the server.

A bank’s Web site can be tested by attempting transactions and then verifying
server logs to ensure that what is seen in the browser is actually happening on
the server.

It is also a good practice to run queries on the database to ensure that the transaction data is being
stored properly.
17. External Interfaces: Some Web systems use external interfaces.

A shop keeper might verify credit card transactions in real-time to avoid frauds.
This case uses an external interface, that is, the shop keeper’s Web site
approaches the bank’s Web site for more information on the credit card used for
any transaction.
Some Web sites send several test transactions using the Web interface. While testing for external
interfaces, try to test the validity of the credit card. If a shop keeper accepts only Visa and
MasterCard, try using an American Express card. The purpose of testing external interface is to
ensure that the software handles every possible message returned by the external server.
18. Error Handling: This is the most often neglected area and hence left untested. Usually, when a
Web site is designed, we give importance to error handling mechanism for our system and not
errors from other systems or unexpected errors. Hence it is important to check what happens if the
site is interrupted in the middle of a transaction.
19. Client Side Compatibility: It has to be ensured that the web application works on all client
machines. To make the Web site accessible to users across the world, the Web site has to be tested
with different combinations of operating systems, browsers, video settings, and modem speed,
which the users across the world may use to access the Web site.

20. Operating Systems: Some operating systems may use fonts that are unavailable on other operating
systems. Hence, make sure that the secondary fonts are available.

Some fonts are not available on both MAC and IBM compatibles.

114 LOVELY PROFESSIONAL UNIVERSITY