I’m currently playing around with SonarQube, an open-source platform for continuous inspection of code quality, and so far, I’ve discovered that it is a lot more interesting than I thought it would be. Therefore, I’ve decided to share my initial findings.
The previous part of this series covered how-to setup JSCover, add test instrumentation, and run some manual tests.
Within this blog, I would like to automate the instrumentation injection step as part of the build process using Gulp.
This post is part one of a series of posts in which I’m covering the basics when it comes to setting up code coverage for JavaScript. There are a lot of intimidating manuals, guides, and confusing blog posts out there, but don’t worry! We will walk through all basics, from installation to automation.
I just recently discovered the Azure Portal Console by accident when deploying (well troubleshooting that is) Umbraco solutions, a topic I will cover later in greater detail within an upcoming series, and was pleasantly surprised. Now the virtual console as included within the Azure Portal isn’t new and therefore perhaps familiar for a lot of you out there, however I haven’t heard of it before.
Recent Comments