T-DOC: A Tool for the Automatic Generation of Testing Documentation for OSS Products

In the context of Open Source Software (OSS), the lack of project documentation is one of the most challenging problems that slows down the widespread diffusion of OSS products. The difficulty of providing up-to-date and reasonable documentation for OSS products relates to two main reasons. First, documenting development activities and technological issues is viewed as a tedious and unrewarding task. Second, data and information about an OSS project (such as source code, project plans, testing requirements, etc.) are scattered and shared via unstructured channels such as unofficial forums and mailing lists.

[1]  Sami Beydeda Research in testing COTS components - built-in testing approaches , 2005, The 3rd ACS/IEEE International Conference onComputer Systems and Applications, 2005..

[2]  Colin Atkinson,et al.  The MORABIT Approach to Runtime Component Testing , 2006, 30th Annual International Computer Software and Applications Conference (COMPSAC'06).

[3]  Jonathan Vincent,et al.  Principles of Built-In-Test for Run-Time-Testability in Component-Based Software Systems , 2002, Software Quality Journal.

[4]  Chengying Mao,et al.  Regression testing for component-based software via built-in test design , 2007, SAC '07.

[5]  Gregg Rothermel,et al.  Using component metacontent to support the regression testing of component-based software , 2001, Proceedings IEEE International Conference on Software Maintenance. ICSM 2001.

[6]  Mauro Pezzè,et al.  Software testing and analysis - process, principles and techniques , 2007 .

[7]  Yingxu Wang,et al.  A method for built-in tests in component-based software maintenance , 1999, Proceedings of the Third European Conference on Software Maintenance and Reengineering (Cat. No. PR00090).