A testing methodology and architecture for computer supported cooperative work software

Despite enormous potential, CSCW software is still immature. In particular, leading researchers in both the CSCW and testing fields have noted CSCW testing tools are nonexistent This thesis contributes a methodology and architecture for execution based testing of CSCW software. The C&barbelow;SCW A&barbelow;pplication MEthodoLOgy for T&barbelow;esting (CAMELOT) provides an organized set of specific techniques that can be used for technological evaluation. The evaluation is organized into two phases: single user and multi-user. Single user evaluation is subdivided further into general computing and human computer interaction. General computing examines software components that provide basic application capabilities. Human computer interaction focuses on the interface between the user and the software application. Multi-user evaluation examines distributed computing and human-human interaction. Distributed computing scrutinizes components responsible for multitasking and multiprocessing in the application at the thread, process, processor and machine level. Human-human interaction focuses on how the software facilitates interaction between users during application use.; Rebecca, our testing architecture contributes to both general and multiuser testing systems. In the area of general testing Rebecca: (1) Provides an extensible component and event model that allows the record/playback of non-GUI events; (2) Allows selective event recording through record filtration; (3) Promotes the integration of the test system into the development environment Outputs test scripts in the developer's native language; (4) Reduces re-recording using component-centric events and runtime component resolution; (5) Simplifies the test process using a simple VCR-like interface.; In the area of multiuser testing Rebecca: (1) Integrates live users into a test session with triggers that playback virtual user behavior based on user interface, state change, timer, or user customized events; (2) Provides runtime configuration of triggers via the threshold models; (3) Simplifies virtual user synchronization with deadlock detection and recovery; (4) Maintains IPC independence, but allows IPC to be recorded; (5) Scales well with a resource conserving architecture.; Our architecture was implemented in Java as a working system called Rebecca-J. The methodology, architecture, and working system were evaluated by testing a mature CSCW application.