Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

On the Distribution of "Simple Stupid Bugs" in Unit Test Files: An Exploratory Study

Presented at: The 18th International Conference on Mining Software Repositories (MSR '21)

Date of Conference: Mon 17 - Wed 19 May 2021
Conference Location: Virtual Conference

  • Be the first to comment

  • Be the first to like this

On the Distribution of "Simple Stupid Bugs" in Unit Test Files: An Exploratory Study

  1. 1. On the Distribution of "Simple Stupid Bugs" in Unit Test Files: An Exploratory Study Anthony Peruma and Christian D. Newman The 18th International Conference on Mining Software Repositories h t t p s : / / s c a n l . o r g
  2. 2. GOAL IMPACT RESEARCH QUESTIONS CONTRIBUTION Explore the quality of test suites from a functional and non-functional perspective Provide developers and tool vendors with insight to better maintain test suites Extent of SStuBs occurring in (non-) test files Co-occurrence of test smells and SStuB fixes Dataset and discussion of test smells and SStuBs in test files
  3. 3. ManySStuBs4J Dataset (Maven Projects) Clone Repository & Source File Extraction Test File Detection Test Smell Detection (tsDetect) ➢ Total volume of Java files with SStuBs: 5,587 ➢ Distribution of SStuBs in file types: 19% test & 81% non-test ➢ Test files: Specific relationships between code and the bug fix: assertion statements time-related identifiers mocking identifiers ➢ Test smells occur in most SStuBs fix test files ➢ Frequently occurring test smell types: Assertion Roulette Exception Handling ➢ Change Numeric Literal SStuBs frequently occur in smelly test files ➢ Test smells are rarely fixed when fixing SStuBs
  4. 4. Potential Code Quality Tools: • Automatic identification of issues in test files based on SStuB fixes to non-test files • Highlight areas of concern based on relationships between SStuBs and code behavior • The quality of test code is as important as the quality of production code • Opens the door for potential future work Do developers proactively address issues in test files? Conclusion & Takeaways

×