A Quick intro to Portal Testing and its Key aspects

1. Testing Enterprise Portals
Sudharshun Ravichander

2. Portal Testing - The First Steps
Before we Begin testing The first steps.
1. Identify Individual Portlets
2. Group by Functionality
3. Group by Performance Needs
4. Group by Source of Portlet Information
5. Identify Information Bottlenecks
6. Identify Interportlet Triggers
7. Identify Portlet Personalization needs
8. Identify Portlet Supported Modes -edit,help etc
9. Identify Deployment Scenarios - Data center Testing, Access Management, Failover etc

3. Portal Testing - The Big Ticket List
1. Inter Portlet Communication

4. Inter Portlet Communication
The The Ability to
Trigger action in
another portlet is Inter
Portlet Communication
- Key Aspect to
Test
Be it Wiring in JSR 168
or Events in JSR 286
High om Testing Priority

5. Portal Testing - The Big Ticket List
2. Themes and Skins

6. Themes and Skins
The Common Header
and Look and Feel
Components which
must be Consistent
across the Portal and
will act as Pallete or
Canvas on which
Portlets Render is
another Important Item
for Testing
Consistency and
Uniformity are Key
Theme elements to look
out for. Being
Responsive is
becoming important as
new devices emerge

7. Portal Testing - The Big Ticket List
3.Customizations

8. Customizations
Customizations are
biggest use cases for
Web Portals. Ability to
Brand and customize
and change every
aspect from layout,
brnading, colors to Look
and feel is a key
element that must be
captured and
accounted for as Key
test Cases in Portal
Testing whether it be be
Global or Page level

9. Portal Testing - The Big Ticket List
4. Portlet Behaviour Isolation

10. Portlet Behaviour Isolation
Portlet Behaviour needs
to be contained to
Portlet.
Portlet reload should
not trigger Page reload.
Action on One portlet
should not cause
another to change
value unless Inter
Portlet Comm Happens.
Test for Individual
Portlet Behaviour

11. Portal Testing - The Big Ticket List
4.Portlet Session Containment

12. Portlet Session Containment
In an era or tabbed
Browsers and Saved
Passwords, It is
paramount that Portlet
Session doesnt get
shared and Each
instance is treated as
separate Session
This is super critical
from Security and
Funcationality
Perspective.
Another Watch item for
Portal testing

13. Portal Testing - The Big Ticket List
5. Portlet Modes

14. Portlet Modes
Portal testing Teams
must identify for each
Portlet a list of
supported modes and
extent of support for
these modes.
Common examples
being edit, help etc

15. Portal Testing - The Big Ticket List
6. Portal Scalability

16. Portal Scalability
Portals and Portlets are windows
to Info aggregated from Multiple
Sources.Include Scalability as a
Thing to keep in mind Throughout
Testing and work closely with
Architects
Given this
Testing Teams must identify
- Data sources
- Bottlenecks
- Performance Gotchas
- Data center Constraints
- Scalability Constraints
- Infrastructure Constraints

17. Portal Testing - The Big Ticket List
6. Automation

18. Automation
Portal Testing presents its own set of
challenges due to dynamic nature of Portal
Applications.
Its not impossible.
Most modern Portal Platforms come with
hook points for unit testing and automation
testing.
Once you have Standardised test
cases..what are you waiting for Automate !!!!
http://www.liferay.com/community/wiki/-
/wiki/1071674/Selenium+Testing

19. Portal Testing - Best of Luck !!!Go for it!!
This presentation was not meant to be comprehensive but provide a quick intro into what are key
aspects of Portal testing.
Before we go our ways, here are some parting Thoughts
For any Succesful Portal Testing Team
- Form - Build a good and solid team
- Storm - Dissect every Design and Brainstorm
- Confirm - Make sure your test cases are robust and confirm to standards
- Perform - Run your test cases
- Inform - Be proactive in bringing up concerns- Portlets are cooperative, you must be too
- Reform - Keep updating test cases and refining test strategy