Portal Testing

Hi,
Can any one tell me whats portal testing?

thanks

Portal testing method includes portal test plan which uses various software and various methods of testing. The main areas of testing which are covered in it are namely: performance testing scalability testing soak testing integration testing availability testing

Hi,
Can any one tell me when will we conduct portal testing?
thanks

[QUOTE=bharathi_ark;2856]Hi,
Can any one tell me when will we conduct portal testing?
thanks[/QUOTE]

I am not getting this discussion.
Whether your project is a portal or simple static website or what so ever.
You have SRS to follow what to test, you have test plan how to test , then why this type of question?

In real Portal testing is not a term related to testing technique.

Hi Friends,
Portal Testing is a kind of Network Testing. Testing the application with the application Protocols (TCP/IP, Http, etc...). According to that Portal Testing is to be conduct. Perl Scripts are used for Portal Testing. Checking the interfaces with different layers..

To test or debug a portal project within the workbench, you must first define a local portal test environment server. Prerequisites: to use a local websphere® portal 5.0 server, you must install the websphere portal 5.0 test environment from the rational® software development platform installation launchpad. To use a local websphere portal 5.1 server, you must install the websphere portal 5.1 test environment using the websphere portal 5.1 cd-rom provided with rational tools. Before using the server, you must configure rational software development platform to use the websphere portal v5.1 test environment. If you update your websphere portal 5.1 test environment (to version 5.1.0.1, or higher) using the rational product updater, you must also delete the previous server definition for the test environment and create a new one for the new server version. To create and configure a portal test environment server: switch to the servers view by selecting window > show view > servers in the servers view, right-click and select new > server. Select localhost as the host name. Select a websphere portal test environment server from the server type list. Click next. On the websphere server configuration settings page, select one of the following values: to use the default http port, select use default port numbers and set the http port number. To use port numbers other than the default numbers used by websphere application server, select use consecutive port numbers and set the first port number. This setting causes the test environment to use sequential port numbers, starting with the number you specify. You must specify a port number that begins a range of port numbers that are not being used by another application. This option allows you to have a remote websphere portal server or websphere application server running on your system, and allows the test environment to use different port numbers. You can also configure the test environment server's http port numbers by editing the server configuration, as explained below. If you are configuring a websphere portal v5.1 test environment server, click next. Enter the portal server settings that you defined when you installed the test environment. Click next. Click finish. Additional options for local test environments can be viewed and changed by double-clicking on the server in the servers view. This opens the server configuration editor. You can change any of the settings that were defined previously. In addition, the portal tab has additional settings which are listed below: select enable base portlets for portal administration and customization to use administration portlets in the test environment. Administration portlets are portlets provided by websphere portal to provide administrative functions, such as portlet installation and configuration. Enable this option only when necessary. It slows down the startup of the test environment. Even when you have enabled the administration portlets, there are limitations. You cannot install portlets using the administration portlets. In addition, most changes that you make are reset to the default values the next time you start the test environment. To debug portlets in a particular layout, use the test and debug options of a portal project, not the administration portlets in the test environment. Select enable multiple pages when deploying portlet projects to allow different portlet projects to use different pages in the portal during testing. By default, multiple pages are enabled. Each portlet project that is associated with a single server will be deployed to a different page. If you want to deploy them all into a single page on the server, you can disable multiple pages when deploying portlet projects. Select enable console logging to redirect log entries to the console. Otherwise, the log entries are written to the <product_installation_root>/runtimes/portal_vxx/log directory, where xx is the version of the websphere portal test environment. Select enable anonymous user access to test portlets in the not-logged-in state. Enter jar file or folder names in the shared library section to make the jar files or the files in the folder available to the server. Save the changes to your server configuration by pressing ctrl + s.

Hi, how to test the jsr 168 complaint portlets in liferay?