Web portal testing - 4

Performance 1.Connection speed Users may differ greatly in connection speed. They may be on a 28.8 modem or on a T3 connection. Users expect longer download times when retrieving demos or programs, but not when requesting a homepage. If the transaction response time is to long, user will leave the site. Other issues to consider are time-out on a page that request logins. If load time is to long, users may be thrown out due to time-out. Database problem may occur if the connection speed is two low, causing data loss. Summary: •Connection speed •Time-out 2.Load What is the estimated number of users per time period and how will it be divided over the period? Will there be peak loads and how will the system react? Can your site handle a large amount of users requesting a certain page? Load testing is done to measure the performance at a given load level to assure that the site work within requirements for performance. The load level may be a certain amount of users using your site at the same time or large amount of data transactions from user such as online ordering. Summary: •Many users requesting a certain page at the same time or using the site simultaneously •Large amount of data from users 3.Stress Stress testing is done in order to actually break a site or a certain feature to determine how the system reacts. Stress tests are designed to push and test system limitations and determine whether the system recovers gracefully from crashes. Hackers often stress systems by providing loads of wrong in-data until it crash and then gain access to it during start-up. Typical areas to test are forms, logins or other information transaction components. Summary: •Performance of memory, CPU, file handling etc. •Error in software, hardware, memory errors (leakage, overwrite or pointers) 4. Continuous use Is the application or certain features going to be used only during certain periods of time or will it be used continuously 24 hours a day 7 days a week? Test that the application is able to perform during those conditions. Will downtime be allowed or is that out of the question? Verify that the application is able to meet the requirements and does not run out of memory or disk space. Security Security is an area of immense extent, and would need extensive writing to be fairly covered. We will no more than point out the most central elements to test. First make sure that you have a correct directory setup. You don’t want users to be able to brows through directories on your server. Logins are very common on today’s web sites, and they must be error free. Make sure to test

How much training will the customer require? .Is the list of specific requirements consistent? 7. •A static web of HTML content.both valid and invalid login names and passwords. Scripting on the server often constitute security holes and are often used by hackers.Is the list of specific requirements compatible with the goals of the organization and the customer? 8.Is anything intentionally left out of this system that the customer might reasonably expect? 4.What is the customer supposed to do with this system? (This could be a list of specific r requirements or features) 3. Summary: •Directory setup •Logins •Time-out •Logfiles •SSL •Scripting Languages Web application types and Questionnaire Checklist 1. When secure socket layers are used.Who is the customer? 2. verify that the encryption is done correctly and check the integrity of the information.How will the customer use this system? (This can be a series of scenarios of the user accomplishing a task or tasks using the system) 10. which will meet those requirements. Verify that relevant information is written to the logfiles and that the information is traceable. The application as: •A set of requirements to be met. Test that it isn’t possible to plant or edit scripts on the server without authorisation.What are the primary risk factors? 5. Are they case sensitive? Is there a limit to how many tries that are allowed? Can it be bypassed by typing the URL to a page inside directly in the browser? Is there a time-out limit within your site? What happens when it’s exceeded? Are users still able to navigate through the site? Logfiles are a very important in order to maintain security at the site.Will a published HTML standard be used to constrain markup? Which one? Will all important customers have browsers which support that standard? 11.This report presents four views into web applications.Is the list of specific requirements complete? 6. or a collection of files to download with no other interaction. •A design. •An "interactive" web consisting of CGI scripts and HTML forms which invoke the scripts Questionnaire Checklist for Requirements 1.How will your customers find out about your application? 9.

Verify that is sent and retrieved in correct form.Does this design impose any new requirements upon the system? The user? The organization? 15. Oracle.External Interface Several web pages have external interfaces. interface and compatibility issues may occur on several areas. then you will be the perfect tester to test web applications :) Keep visiting www. that provide and extend functionality and effects for the web application. Application severs typically contains objects such as programs. scripts. •Compatibility of server software. network connections •Database compatibility (SQL. Sybase etc. Issues to test: •Verify that communication is done correctly.Are all the specific requirements supported in this design? 14. application servers and database servers (and possibly mail servers). Client Side compatibility . is it amenable to separate systems for development. server software or network connections. for example. website testing Web portal testing . DLLs or third party products. Depending on the configuration of the server side compatibility issues may occur depending on. 0 comments Labels: web portal testing.) 2.Is there any provision for robots to visit and index your site? This is the conclusion of web portal testing postings and am ending with this post.pris.3 Server Side Interface 1. separate operating environments? In other words. web server-application server.12. hardware.Server Interface Due to the complex architecture of web systems. Web servers normally hosts HTML pages and other web services. Database compatibility issues may occur depending on different database types (SQL.Does this design allow for multiple.).com Will be back soon with another intresting topic. If you got good idea on all web portal testing posts. Oracle. Sybase etc. server hardware.testingfinder. application serverdatabase server and vice versa. such as merchants verifying credit card numbers to allow transactions to be made or a site like http://www. testing and production? 17. Test the communication between the different servers by making transactions and view logfiles to verify the result.nu/ that compares prices and delivery times on different merchants on the web.Is privacy an issue? User authentication? How are these issues handled? 16. The core components are web servers.Were all practical alternatives considered? 13.

Browsers The browser is the most central component on the client side of the web. Different browsers also have different settings for e. is a Microsoft product and therefore designed for Internet Explorer.Platform There are several different operating systems that are being used on the market today.X) •AOL •Browser settings (security settings.X.) •Colour depth (256. Try and vary the following: •Screen resolution (check that text and graphic alignment still work. foreground and background . ActiveX controls. ActiveX. 32-bit) 4. or not at all. font are readable etc.X. NT) •Unix (different sets) •Macintosh •Linux 2. security or Java support.9. printing is done more than ever. JavaScript.X) •Opera (8.g.4. for example Applets.X. 2000.8.7. ActiveX.) •Frames and Cascade Style sheets •Applets.X. scripting. while JavaScript is produced by Netscape and Java by Sun.X. 98. Summary: •Internet Explorer (5. DHTML.6.X.X) •Netscape Navigator (3. plugins or different HTML specifications. Preferences Depending on settings and preferences of the client machine.6.1.3. but fail under another.X) •Mozilla Firefox (2. compatibility issues may occur. graphics. 16-bit.X. This substantiates the fact that compatibility problems commonly occur. Java etc.Settings.Printing Despite the paperless society the web was to introduce. web applications may behave differently. Different applications may work fine under certain operating systems. Verify that pages are printable with considerations on: •Text and image alignment •Colours of text. Frames and Cascading style sheets may display differently on different browsers. Browsers come in different brands and versions and have different support for Java. client side scripting •HTML specifications •Graphics 3. for example. The following are the most commonly used: •Windows (95. A good way to test browser compatibility is to create a compatibility matrix where different brands and versions of browsers are tested to a certain number of components and settings. ActiveX controls or cookies. and depending on the configuration of the user system.

As soon as the hierarchy of the site is determined. Another important aspect of navigation is if the site is consistent in its conventions regarding page layout. They rarely take the time to learn about the sites structure.•Scalability to fit paper size •Tables and borders 0 comments Labels: manual testing. Is the application’s navigation intuitive? Are the main features of the site accessible from the main page? Do the site need a site map. navigation bars. Too much information often has the opposite effect as to what was intended. Issues to check are: • Make sure that the graphics serve a definite purpose and that images or animations don’t just clutter up the visual design and waste bandwidth • Verify that fonts are consistent in style • Suitable background colours combined with font. software testing. Make sure that users intuitively know that they are still within the site by keeping the page design uniform throughout the site. and it is therefore important to keep the navigational help as concise as possible.) 2. lists. animations. borders.and foreground colour. Users of the web tend to be very goal driven and scan a site very quickly to see if it meets their expectations.g. colours. If not. search engine. web portal testing. links. Testing tools. between different user interface controls (buttons. boxes. menus. Summary: • Intuitive navigation • Main features accessible from main page • Site map or other navigational help • Consistent conventions (navigation bars. Have real users try and navigate through ordinary papers describing how the layout is done. menus. Remember that a computer display exceptionally well presents contrasts apposed to printed paper • Three-dimensional effects on buttons often gives useful cues • When displaying large amount of images. backgrounds. consider using thumbnails.). Check that the original picture appears when a thumbnail is clicked • Size – quality of pictures. fonts. they quickly move on.Graphics The graphics of a web site include images. or other navigational help. links etc. buttons etc. To determine whether or not your page is easy to navigate through consider the following. usage of compressed formats (JPG or GIF) • Mouse-over effects . website testing Web portal testing -2 Usability 1. movie clips.Navigation Navigation describes the way users navigate within a page. windows etc. Be careful though that you don’t over do your site. or between pages via e. links etc. testing of how users navigate can commence.

website testing Web portal testing .1 Portal Test Areas: Following are the main areas to test when developing and publishing a web site. Content testing should be done as early as possible.check that the link takes you to the page it said it would. Linkage testing is divided into three sub areas. These kinds of verifications are often done in e. It’s easy to get fond of ones own solution. Third . The accuracy of the information is whether it is without grammatical or spelling errors. Second – That the link isn’t broken i. It is a checklist that presents the most important features to test under each area and how to perform them.e. First . make sure that the main area is large enough • Consider size of pages. Several screens on the same page or links between them • Do features on the site need help systems or will they be intuitive 0 comments Labels: manual testing. so having actual users evaluating the site may be critical. i. or in a database. in forms of text. images or animations. Too much design can easily turn a conservative corporate site in to a publicity stunt. For example wrong prices in a price list may cause financial problems or even induce legal issues. Summary: • Correctness • Accuracy • Relevancy 4. Word or other word processors.Content Content testing is done to verify the correctness. Functionality testing 1. Important to all kinds of usability tests is to involve external personnel that have little or no connection to the development of the site. Testing tools. This may otherwise cause misunderstandings or confusion. when the information is posted. Correctness is whether the information is truthful or contains misinformation. They constitute the mean of transport between pages and guide the user to certain addresses without the user knowing the actual address itself. Summary: • Intuitive design • Consistent design • If using frames. that the page you’re linking to exists. Remove irrelevant information from your site. software testing. web portal testing.e. accuracy and relevancy of information presented on the site.g.3. Links Links are maybe the main feature on web sites.General Appearance Does the site feel right when using it? Do you intuitively know where to look for information? Is the design consistent throughout the site? Make sure that the design and aim goes hand in hand.

Verify that the information that is to be retrieved is there. for example. These controls can be done both on the client side as well as the server side. login info • Users denying or accepting • Temporary and expired cookies . which in turn gets processed and acted upon in some way. verify the correctness of the value. If default values are used. How will temporary cookies be handled? What will happen when cookies expire? Depending on what cookies are used for. Check that invalid inputs are detected and handled. Summary: • Information hits the server in correct form • Acceptance of invalid input • Handling of wrong input (both client an server side) • Optional versus mandatory fields • Input longer than field allows • Radio buttons • Default values 3.– Ensure that you have no orphan pages at your site. If the forms are designed to only accept certain values this should also be tested for. if only certain characters should be accepted. the web server sends information about the user and stores it on the client computer in form of a cookie. JavaScript or VBScript.g. Remember that to reduce redundant testing. Forms Forms are used to submit information from the user to the host. Summary: • Verify that you end up at the designated page • Verify that the link isn’t broken • Locate orphan pages if present 2. Testing the integrity of the submitting operation should be done in order to verify that the information hits the server in correct form. for example using scripting languages such as Jscript. depending on how the application is designed. When a user accesses a site that uses cookies. login info. For example. These can be used to create more dynamic and custom-made pages or by storing. try to override this when testing. they need to be checked. Cookies Cookies are often used to store information about the user and his actions on a particular site. there is no need to test a link more than once to a specific page if it appears on several pages. how does it respond to users that disabled the use of such? Does it still function or will the user get notified of the current situation. Summary: • Encryption of e. If your applications require cookies. it needs only to be tested once. An orphan page is a page that has no links to it. and may therefore only be reached if you know the correct URL. one should examine the possibilities for other solutions. If login information is stored in cookies check for correct encryption of these. If you have designed your site to use cookies.

Java. JavaScript. . The issue here is to test and verify the function of the components. Resources: http://arealvalidator. Summary: • Meta tags • Frames • HTML syntax • Passwords • Dynamically created pages 5. Except HTML classes. depending on the application. Java.html. JavaScript. these tests can be done as early as possible in the development process. Demands for more dynamic features. VBScript or Perl need to be verified. free or by payment. The most important include Java applets. ShockWave or RealPlayer). online as well as for download. Summary: • Language specifications • Language syntax (HTML.g. ActiveX controls. Since this kind of testing is done by static analysis tools and needs no actual running of the code. for instance. ActiveX. SQL etc. Dynamic Interface Components Web pages are not just presented in static HTML anymore.com/ http://www.) 6. C++. are geographically separated. When development is done in a distributed environment where developers.0)? How strictly? When HTML is generated dynamically it is important to know how it is generated. frames. this kind of check is often done by the compiling program. VBScript.com/web/purify. Make sure that specifications are well spread throughout the development organization to avoid future problems. Depending on how the site is designed using Meta tags. which HTML specification will be used (for example 3.2 or 4.4. dynamically created pages. Programming Language Differences in web programming language versions or specifications can cause serious problems on both client or server side. passwords or different languages.g. For languages that need compiling e. CSS and third-party plug-ins (QuickTime. HTML syntax. C++. Dynamic Interface Components reside and operate both on server and client side of the web. specifications on e. this area becomes increasingly important. For example. Java Servlets. There are several tools on the market for validating different programming languages. CGI.delorie. ASP. Web Indexing There are a number of different techniques and algorithms used by different search engines to search the Internet. Scripting languages. your site will be searchable in different ways. Language validation tools can be found in compilers. custom made sites and high interactivity have made the Internet a more vivid place than before.

ActiveX. The issue is to test the functionality of the database.com/search/label/website%20testing#ixzz0zugkT7Tx GET –Requests a representation of the specified resource. In general. input longer than field etc. Issues to test are: • Creation of tables • Indexing of data • Writing and editing in tables (for example valid numbers or characters.g. Example .e. there are two types of errors that may occur. event logging (logfiles) can be used to record events by applications on the server side in order to determine functionality. retrieving or editing in the database is performed in a correct way. server-side scripting etc. retrieve and editing of information. Data integrity errors refer to missing or wrong data in tables and output errors are errors in writing.) function as intended (i. The most commonly used type of database in web applications is the relational database and it’s managed by SQL to write. data integrity errors and output errors. scripts etc. Java-Servlets.not compatibility issues. This may result in the creation of a new resource or the updates of existing resources or both. An example of what to test can be a Java applet constructing and displaying a chart of company statistics. Since server-side components don’t have user interface. which should not need to consider the side effects that a request should cause. JavaScript. such as using it for taking actions in web applications. Resources: Java Specific tools: JavaSpec and JavaStar. One reason for this is that GET may be used arbitrarily by robots or crawlers. The data is included in the body of the request. editing or reading operations in the tables.e. from an HTML form) to the identified resource. CSS etc.) • Reading from tables Read more: http://www. writing. where the information first have to be retrieved and then interpreted and displayed on the screen. ActiveX controls. Verify that queries. running queries and fulfilling user requests for data storage. not the content and the focus here is therefore on output errors. Note that GET should not be used for operations that cause side-effects. do the components perform the right tasks in a correct way) 7.) function as intended (i.testingfinder.) • Do server side components (ASP. Summary: • Do client side components (applets. POST –Submits data to be processed (e.. housing the content that the web application manages. do the components perform the right tasks in a correct way) • User disabling features (Java-applets. Databases Databases play an important role in web application technology.

202 Accepted .Standard response for successful HTTP requests. and accepted.200 OK . 100 Continue –This means that the server has received the request headers. . understood. This class of status code indicates that the client's request was successfully received.HTTP status codes HTTP status codes-1 1xx Class. understood. Informational. and that the client should proceed to send the request body 101 Switching Protocols 102 Processing 122 Request-URI too long HTTP status codes-2 2xx Class Success The action was successfully received. and accepted. continuing process. This class of status code indicates a provisional response. Means Request received. used in experimental conditions only.

For instance. but popular browsers implemented it as a 303 See Other. .0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily").1 added status codes 303 and 307 to disambiguate between the two behaviors.301 Moved Permanently –This and all future requests should be directed to the given URI. HTTP/1. as it might be disallowed when processing actually takes place. but also an example of industrial practice contradicting the standard.The client must take additional action to complete the request.This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. the request should be repeated with another URI. HTTP/1.307 Temporary Redirect (since HTTP/1.1) . but future requests can still use the original URI.305 Use Proxy (since HTTP/1. HTTP status codes-4 4xx Class Client Error The 4xx class of status code is intended for cases in which the client seems to have erred.203 Non-Authoritative Information (since HTTP/1. In contrast to 303. . . primarily for security reasons. . . However.302 Found –This is the most popular redirect code. a POST request must be repeated using another POST request. but the processing has not been completed. The request might or might not eventually be acted upon. . 400 Bad Request .1) –Many HTTP clients (such as Mozilla and Internet Explorer) don't correctly handle responses with this status code. the request method should not be changed when reissuing the original request.204 No Content HTTP status codes-3 . Therefore. These are typically the most common error codes encountered while online..1) –In this occasion.3xx Redirection . the majority of Web applications and frameworks still use the 302 status code as if it were the 303.The request has been accepted for processing.

but specifically for use when authentication is possible but has failed or not yet been provided.–The request contains bad syntax or cannot be fulfilled. Unlike a 401 Unauthorized response. Subsequent requests by the client are permissible. 403 Forbidden –The request was a legal request. but the server is refusing to respond to it. 401 Unauthorized –Similar to 403 Forbidden. 404 Not Found –The requested resource could not be found but may be available again in the future. authenticating will make no difference. .

Sign up to vote on this title
UsefulNot useful