[cosmo-dev] External testing resource wishlist

[Randy Letness]

Travis Vachon wrote:
> Hi folks
>
> I chatted with Nitin Gupta last week about the availability of QA 
> resources within his company for improving our unit and functional 
> testing, with the additional goal of introducing his staff to both 
> modern testing tools and the calendaring space in general. I'd like to 
> compile a somewhat coherent list of areas we'd like to see additional 
> testing in so they're able to get started.
>
> I think the best compromise between Nitin's goals and our needs can be 
> found in JUnit testing and additional protocol tests. With that in 
> mind, I'd like to solicit ideas for what parts of the server would be 
> most helped by additional testing. In particular, answers to the 
> following questions from knowledgeable parties would be useful:
>
> 1) Which (probably plural) of our protocols could use additional 
> testing versus the relevant specification?

Caldav for sure.  Atom and morse code could use more protocol level 
testing, but a bunch of testing is covered in the windmill tests (for 
atom protocol) and chandler sharing tests (for morse code).  More 
security tests at the protocol level would be great.  That is, making 
sure a user's data can't be access by others (unless ticket is involved).

> 2) Which components inside the server could use additional component 
> testing?
>

The account browser could use some tests.  That is the one component 
that constantly breaks due to changes because there is hardly any test 
coverage.

> 3) Where in the server would additional unit tests be helpful?

Off hand I can think of:

org.osaf.cosmo.mc.* (morse code controller code)
org.osaf.cosmo.hibernate.* (hibernate extensions)
org.osaf.cosmo.xml.* (xml utilities)

-Randy