Introducing Automated Unit T esting into Open Source Projects - - PowerPoint PPT Presentation

▶
introducing automated unit t esting into open source
SMART_READER_LITE
LIVE PREVIEW

Introducing Automated Unit T esting into Open Source Projects - - PowerPoint PPT Presentation

Sep 16, 2023 103 likes •225 views

Failing test cases Passing test cases 250 200 Tests 150 100 50 A M J J A S O N D J F M A M J J A S O N D J F M A M J J A 2007 2008 2009 Month Introducing Automated Unit T esting into Open Source Projects

slide-1
SLIDE 1

Month Tests

50 100 150 200 250 A M J 2007 J A S O N D J F M A M J 2008 J A S O N D J F M A M J 2009 J A

Failing test cases Passing test cases

Introducing Automated Unit T esting into Open Source Projects

Christopher Oezbek

Freie Universität Berlin The 6th International Conference on Open Source Systems, 2010-05-30 - 2010-06-02

slide-2
SLIDE 2

Study Design

◮ Goal: Explore Innovation Introduction in OSS ◮ Innovation: Automated Unit T

esting via JUnit

◮ T

arget Project: FreeCol

◮ Prescribed Phases:

◮ Lurk ◮ Code & Collaborate ◮ Withdraw ◮ Observe , christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 2

slide-3
SLIDE 3

Results I - Number of T ests

Month Tests

50 100 150 200 250 A M J 2007 J A S O N D J F M A M J 2008 J A S O N D J F M A M J 2009 J A

Failing test cases Passing test cases

Introduction Period

◮ After the intervention more than 200 additional tests

were created

, christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 3

slide-4
SLIDE 4

Results II - Concepts

◮ The role of signaling in innovation introduction ◮ Learning behavior in OSS projects ◮ Other results:

◮ T

est cases as a communication device

◮ The role of the test-masters , christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 4

slide-5
SLIDE 5

Signaling

Date

Innovator Communication Test Commits

A p r 7 M a y 7 J u n 7 J u l 7 A u g 7 S e p 7 O c t 7 N

  • v

7 D e c 7 J a n 8 F e b 8 M a r 8

  • ●
  • ●
  • ◮ First withdrawal failed to transfer responsibility

◮ Explicit signaling can provide necessary awareness

, christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 5

slide-6
SLIDE 6

Learning behavior

Month Commits per month

5 10 15 A M J 2007 J A S O N D J F M A M J 2008 J A S O N D J F M A M J 2009 J A

Others

5 10 15

Core Developers

5 10 15

Test Masters

5 10 15

Maintainers

◮ T

esting done by only a small proportion of developers

◮ Affinity to testing appears static over time

, christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 6

slide-7
SLIDE 7

Summary

  • 1. Demonstrated the feasibility of introducing an

innovation

  • 2. Presence is informally managed ⇒ signaling

recommended

  • 3. Hypothesized: Learning behavior in OSSD is limited

, christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 7

slide-8
SLIDE 8

Introducing T esting into OSS Projects

Thank you

christopher.oezbek@fu-berlin.de

, christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 8

slide-9
SLIDE 9

Backup Slides

, christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 9

slide-10
SLIDE 10

Results - Coverage

Month Percentage of LOC covered by tests per package

10 20 30 40 50 A M J 2007 J A S O N D J F M A M J 2008 J A S O N D J F M A M J 2009 J A

Business Model Server Artificial Intelligence Other User Interface

, christopher.oezbek@fu-berlin.de, Introducing Unit T esting, OSS 2010 10