|
|
| [1] Saying, « I am testing » is enough to improve the product: An empirical study |
| Authors: |
Robillard, P.N., François-Brosseau, T. |
| Reference: |
The Second International Multi-Conference on Computing in the Global Information Technology (IEEE), ICCGI 2007 |
| Page(s): |
x-x |
| Date/Year: |
Mar. 2007 |
| None available. |
|
| [2] A General Model of Unit Testing Efficacy |
| Authors: |
Houman Younessi; Panlop Zeephongsekul; Winai Bodhisuwan |
| Reference: |
Software Quality Journal 10(1) |
| Page(s): |
69-92 |
| Date/Year: |
Jul 2002 |
| In this paper, we report on the results of research conducted to develop a predictive model of the efficacy of one important defect management technique, that of unit testing. We have taken an empirical approach. We commence with a number of assumptions that led to a theoretical model which describes the relationship between effort expended and the number of defects remaining in a software code module tested (the latter measure being termed correctness). |
|
| [3] Managing the test process [software testing] |
| Authors: |
Davis, G. |
| Reference: |
Software Methods and Tools, 2000. SMT 2000. Proceedings. International Conference on |
| Page(s): |
119-126 |
| Date/Year: |
2000 |
| The paper, whilst not attempting to introduce new material into the equation, discusses various testing concepts from an industry perspective. |
|
| [4] On the determination of an appropriate time for ending the software testing process |
| Authors: |
Malevris, N.; Petrova, E. |
| Reference: |
Quality Software, 2000. Proceedings. First Asia-Pacific Conference on |
| Page(s): |
81-88 |
| Date/Year: |
2000 |
| In this paper, a stopping rule that indicates the appropriate time at which to stop testing is presented. The rule automatically adapts to modifications in the assumptions, since it can be applied under any software error-counting model. |
|
| [5] Diversity in the software development process |
| Authors: |
Hilford, V.; Lyu, M.R.; Cukic, B.; Jamoussi, A.; Bastani, F.B. |
| Reference: |
Object-Oriented Real-Time Dependable Systems, 1997. Proceedings., Third International Workshop on |
| Page(s): |
129-136 |
| Date/Year: |
1997 |
| The two best-known methods of building fault-tolerant software are n-version programming and recovery blocks. To tolerate faults, both of these techniques rely on design diversity, i.e. the availability of multiple implementations of a specification. Software engineers assume that the different implementations use different designs and, thereby, it is hoped, contain different faults. Our study uses a novel method of incorporating diversity in the development of one version of the software. We term this approach the pipeline method of software development. |
|
| [6] Developing a Testing Maturity Model for software test process evaluation and improvement |
| Authors: |
Burnstein, I.; Suwanassart, T.; Carlson, R. |
| Reference: |
Test Conference, 1996. Proceedings., International |
| Page(s): |
581-589 |
| Date/Year: |
1996 |
| We are developing a Testing Maturity Model (TMM) to address these issues. In this paper we discuss our approach to TMM development, the major features of the TMM, its ties to the Capability Maturity Model, and our initial plans for a Testers' Tool Workbench that will support testing process maturity growth. |
|
|
|
