Nowadays, a Quality testing team is facing challenges to sustain its core activities and the same level of quality while new features, new platforms, more complex use cases are to covered.The Glassfish Quality Community is an initiative which intends to build a testing community around the Glassfish project and attempts to address the above challenges. This session will present in details what the Glassfish Quality community is all about and what directions have been taken to meet its objectives

1. Glassfish Quality
Community
Pascal Prévot
Software Quality Manager
SUN Microsystems
1

2. Agenda
What is GlassFish?
Test Challenge in Open Source
FishCAT Program
Student Program
Main outcomes
2

3. What is GlassFish ?
● Application Server (Middleware)
● Java EE 5, 6 Reference Implementation
● Enterprise functionality
● Open Source product
● A strong community (more than 7,000 members)
● Users, partners, testers, developers
● Started in 2005
3

4. GlassFish / Java EE adoption
Total GlassFish Registrations
Goal - 250K Total Unique GlassFish Registered Users Target Unique Registered
Users - FY'09
Total Unique Registered Users
•Over 14 million downloads in less than 2 years
500
•Over 7,000 members
400
•1200 Registrations per / day (over 300K in 18 months)
300
•Over 2500 mail messages / per month
200
Y/Y Dow nload Grow th
100 12000000
J'08
A'08
S'08
O'08
N'08
D'08
J'09
F'09
M'09
A'09
M'09
J'09
10000000
8000000
Add. Forcast
YTD
6000000
4000000
2000000
0
FY 06 FY 07 FY 08 FY 09
4

5. Test challenges in Open source
Active Open source products change very rapidly with new
features added by external contributors
• How to ensure QA teams test new bits on a timely fashion?
• How to make sure new deliveries are of good quality?
Open source products can be configured in many ways:
• How to validate all the relevant combinations?
• How to determine real life configurations?
Quality coverage increases over time to take into account
new features, new supported platforms, ...
• … while having to maintain an existing base of tests
• … at constant QA resource staffing
5

6. GlassFish QA Community goals
Students Communities
• Enhance overall GlassFish quality
> More test cases for higher coverage Testers / ISV's
> Testing engagement during projects
• Inject “Voice of the customer” into GlassFish Quality
> Tested End-user configurations
> Concrete customers scenarios
• Increase GlassFish adoption in the IT industry
> Early adopters in the development cycle
> Awareness in the universities
6

7. FishCAT program
Early access program
• Field testing of the GlassFish project
• Window of opportunity to provide direct feedbacks to
engineers while the project is still under development
• Performed while GlassFish QA continues testing
> Ability to anticipate issues on real life scenarios
Process
• The GlassFish QA team drives the community:
> Weekly meetings
> Recommended tasks based on areas of expertise
• Transparent email discussion in the community
• Shared bug tracking system
> Leadership, responsiveness and transparency
A Win-Win program to improve GlassFish quality
7

8. Student program
An opportunity to learn
● Mentor Master level projects leading to developments in
GlassFish
● Quality courses based on GlassFish
> Strong links with universities to communicate on
SUN portfolio and our Quality approach
An engagement to contribute
• Bug filing in the GlassFish project
• Students develop automated tests in dedicated areas
• Opportunity to interact with Sun Engineers on real projects
and be an active GlassFish contributer after graduation.
> Win-win deal where GlassFish quality improves
while students increase their experience
A proactive approach to increase GlassFish awareness
and adoption in the future developer community
8

9. Main outcomes
• 32 professionals from 18 different countries
• 125 defects submitted, 94% resolved. 5 manuals
FishCAT reviewed
• More than 700 emails exchanged
• Influenced universities to teach QA based on
GlassFish. QA class students filed more than 250 bugs
Students • Mentored university students in developing cool
technologies based on GlassFish. 50+ Students are
working on more than 25 projects.
9

10. FishCAT - Success Factors
• Constantly engage the community in testing
> Identify key contributors and reward them
> Setup win-win situations where feedbacks / issues are
promptly taken into account
• Create a transparent environment for sharing
> State goals of the required efforts
> Share your defect tracking system, defect resolution
stages, test cycle information
> Pro-actively communicate with the community on any
relevant topic. Be clear and unambiguous !
10

11. Students - Success Factors
• Effective link between students and SUN engineers
> Keep up interest so that students don't feel isolated
> Solid reference in student resumes
• Concrete projects
> Students are saving time without building the sample
applications/projects during testing.
> They can make practical use of the GlassFish popular
open source components during their testing courses.
11

12. References
• GlassFish project
http://glassfish.org
• GlassFish Aquarium
http://blogs.sun.com/theaquarium
• GlassFish Quality Community
http://glassfish.org/quality
• FishCAT program
http://wiki.glassfish.java.net/Wiki.jsp?page=FishCAT
12

13. 13