Tech Trek: A Software Engineer's Guide to Code and Beyond

In my previous blog , we have already seen how to setup SonarQube server on Windows 10. In this blog, I’ll show you how to generate sonar report using SonarScanner.  Step to setup SonarQube Download SonarScanner from https://docs.sonarqube.org/latest/analysis/scan/sonarscanner/ . Set SonarScanner to PATH under Environment Variable. Unzip it and open sonar-scanner.properties which are under conf directory. Edit the below lines Now, go to your project folder directory, open command prompt and run sonar-scanner.bat. It will do the analysis and then post the result to the SonarQube server http://locathost:9000/ having the project name as sonar key that we have configured in sonar-scanner.properties file. You can check the JUnit test code coverage as well by clicking on Coverage. Happy Coding..!!!

Overview SonarQube is an automatic code review tool to detect bugs, vulnerabilities and code smell in your code. It can integrate with your existing workflow to enable continuous code inspection across your project branches and pull requests.  Prerequisite Make sure you have JAVA 11 or higher version installed on your window machine. Step to setup SonarQube Download Community edition from https://www.sonarqube.org/downloads/ Extract it and go to the bin folder. Choose windows-x86–32 or windows-x86–64 based on your machine configuration. Run StartSonar.bat which will start the SonarQube server.  Open browser and hit http://localhost:9000 If you want, you can start the sonarQube server to a different port by just updating the port number (sonar.web.port=9070) to sonar.properties which is present under conf directory. You can login to the portal using default credential (admin:admin). Congratulation! SonarQube server is up and running on loca...

I have seen many people using POSTMAN tools but very few of them know how to exactly use all the features of POSTMAN application. So, in this article, I am going to share a few tips/tricks which can be really helpful in our API testing. Set Environment Variables Let’s assume we have an endpoint to get some data after authenticating yourself bypassing username/password. Now, you have to test this endpoint which is deployed on multiple environments like a local machine, test environment and on SIT environment as well. Also, the credential is different for each environment. So, how are we going to test it? Most of the time, I have seen that people create one-one requests for each environment or create one request and then modify the existing username/password and hostname to point to a different environment. The Simple Solution is to set changing parameters as an Environment variable and switch environment to test for different regions. E.g.  http://<HOSTNAME:POST>/t...