
doi: 10.1109/icst.2009.32
As computers with multi-core CPUs become the norm, software development professionals must confront the challenge of developing software that takes advantage of this hardware trend. API providers, in turn, must provide useful parallel programming libraries. PLINQ, a parallel version of Microsoft's LINQ-to-Objects, is one such API aimed at providing a simple, functional style programming model for parallelism. At Microsoft, we have multiple testing strategies for the software components we develop. We present in this paper one approach to testing PLINQ using an automated test generation, execution, and evaluation strategy named SLUG (Systematic LINQ Unit-test Generator). This approach enables us to not only generate unit tests, but performance, stress, and security tests as well. We show that by using this approach to testing, we can achieve high code coverage; we analyze how SLUG allowed us to gain a higher confidence in the quality of our code.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 6 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
