Last week, my recent paper: Making Offline Analyses Continuous has been accepted to ESEC/FSE 2013. The paper is in collaboration with Yuriy Brun, Michael D. Ernst, and David Notkin.
Put simply, the paper proposes a framework that considers existing analyses that work on program source code as black boxes. Using these black box analyses, then an author can implement a wrapper that transforms the analysis into an IDE-integrated continuous one. All ugly details about how concurrent developer edits are handled, when the analysis is run, and how the results are updated and shown to the developer are either completely handled by the framework or represented in the wrapper through a high-level API.
The framework is prototyped for Eclipse: https://bitbucket.org/kivancmuslu/solstice
Also, check out the example continuous analyses implemented so far:
Put simply, the paper proposes a framework that considers existing analyses that work on program source code as black boxes. Using these black box analyses, then an author can implement a wrapper that transforms the analysis into an IDE-integrated continuous one. All ugly details about how concurrent developer edits are handled, when the analysis is run, and how the results are updated and shown to the developer are either completely handled by the framework or represented in the wrapper through a high-level API.
The framework is prototyped for Eclipse: https://bitbucket.org/kivancmuslu/solstice
Also, check out the example continuous analyses implemented so far:
- Continuous testing: https://bitbucket.org/kivancmuslu/solstice-continuous-testing
- Continuous FindBugs: https://bitbucket.org/kivancmuslu/solstice-continuous-findbugs
- Continuous PMD: https://bitbucket.org/kivancmuslu/solstice-continuous-pmd
RSS Feed
