QA has always been an advantage of JBoss Portal over other open-source portals: we've had strong coverage of databases and LDAP servers with the JBoss Portal 2.x series in addition to specification implementation and unit tests. However, we're not stopping there. We're always looking for ways to improve JBoss Portal's quality, and one way to accomplish this is better testsuite coverage. Here's an overview of our QA work:
- Testsuite coverage
We have continuous run of portal 2.6 testsuite and trunk testsuite against JBoss 4.2.0.GA. Results can be seen at 2.6-testuite and trunk-testsuite. We plan to add JBoss AS 4.2.1.GA to the matrix as well.
- Database Compatibility
We've been continuously running our testsuite against following the most popular database products for over a year now:
- Oracle 9i
- Oracle 10g
- MySql4
- MySql5
- MS SQL Server
- PostgreSQL 8
- Hypsersonic (HSQLDB)
The result of these test runs can be seen at DB-tests.
- LDAP compatibility
LDAP support has been added in the 2.6 release and we've also had continuous runs of identity module tests with the following LDAP servers:
- OpenLDAP
- RedHat DS (of course)
- Sun DS
- Open DS
The test results can be seen at ldap-tests.
- Modules detachment
I won't speak here about the detachment of modules since Julien covered it nicely in another post already. It is the last item that has been added to the mix, just a couple of days ago. The following modules have been detached from the trunk source tree so far and they are used in portal as thirdparty libraries:
Basically it is about modularizing the code base and make it container agnostic. As a result, we now have continuous runs of these modules test suites against JBoss AS 4.2.0.GA, JBoss AS 4.2.1.GA and Tomcat 6. We plan to add JBoss 5 and Tomcat 5.5 very soon to the matrix.
- Interoperability with other portal servers
This effort is still in its early stages. We have started doing some deeper testing of WSRP interoperability with BEA portal server. We plan to try to make it part of a continuous run and include more vendors as well. This might prove tricky and the lack of a TCK for WSRP makes interoperability testing rather dauting.
A portal is a key integration product for enterprise applications and it should be tested with the different products it integrates with. If you need a portal and you worry about how it will behave in your environment, a continuously run, well covering test suite is a major factor for your peace of mind. QA is a necessary evil and, as you can see, we are serious about it. How does your current portal compare (if you're not already using JBoss Portal, that is ^_^)?
