DeepAI AI Chat
Log In Sign Up

How Different is Test Case Prioritization for Open and Closed Source Projects?

by   Xiao Ling, et al.
NC State University

Improved test case prioritization means that software developers can detect and fix more software faults sooner than usual. But is there one "best" prioritization algorithm? Or do different kinds of projects deserve special kinds of prioritization? To answer these questions, this paper applies nine prioritization schemes to 31 projects that range from (a) highly rated open-source Github projects to (b) computational science software to (c) a closed-source project. We find that prioritization approaches that work best for open-source projects can work worst for the closed-source project (and vice versa). From these experiments, we conclude that (a) it is ill-advised to always apply one prioritization scheme to all projects since (b) prioritization requires tuning to different project types.


page 1

page 2

page 3

page 4


Why We Engage in FLOSS: Answers from Core Developers

The maintenance and evolution of Free/Libre Open Source Software (FLOSS)...

Quality Classifiers for Open Source Software Repositories

Open Source Software (OSS) often relies on large repositories, like Sour...

OSC Community Lab: The Integration Test Bed for O-RAN Software Community

O-RAN Software Community (OSC) is an open-source project collaborated by...

A decentralized method for making sensor measurements tamper-proof to support open science applications

Open science has become a synonym for modern, digital and inclusive scie...

DockerMock: Pre-Build Detection of Dockerfile Faults through Mocking Instruction Execution

Continuous Integration (CI) and Continuous Deployment (CD) are widely ad...

How do Developers Promote Open Source Projects?

Open source projects have an increasing importance on modern software de...

Understanding Emotions of Developer Community Towards Software Documentation

The availability of open-source projects facilitates developers to contr...