The UpgradeJS Blog

SonarQube is an open-source platform developed by SonarSource that provides continuous inspection of code quality through static code analysis.

There are two ways to set up SonarQube analysis - you can select from the cloud solution (sonarcloud) or install a SonarQube instance on your machine or a remote server. In the first chapter we set up a local SonarQube instance and ran the analysis for a simple JavaScript application

In this chapter, we will continue to work with the same application and add more features to it.

When we test our applications, it’s often useful to use more than one tool or framework for different kinds of tests.

For example, in a Backend-for-Frontend (BFF) application, we may have end-to-end (e2e) tests and unit tests. We might use a tool like Cypress for e2e testing and Jest for unit testing.

Each of these tools can produce a test coverage report, but wouldn’t it be nice to be able to combine all our test coverage data into one report? With IstanbulJS, we can!

In this article, I’ll show you how.

When we run tests, we don’t want to hit external services in most cases, so our tests don’t depend on external services and are more stable. We can use gems like VCR or WebMock to stub the requests that are done by the Rails application, but when the request is initiated by the JavaScript code… that’s a different story.