1

I am fan of improving the quality not only of the product I test but also for the test itself.

I want to create other customized rules for integrating with sonarqube that does not exist in classic tools.

Any suggestions? Thanks in advance

  • can you elaborate on what you are using in sonarqube.. I enabled coding rules, test coverage, code duplication, complexity, and architecture – niartseoj Jun 21 '18 at 19:43
  • I don't understand what you're asking - can you elaborate a little? – trashpanda Jun 22 '18 at 8:53
  • I m searching for rules that we can use with static analysis tools like complexity, Duplicate code detection, metrics about quality .... I want to add customized rules to test my automated script code (static testing) – Emna Jun 22 '18 at 9:02
  • Great to add complexity, thanks. Other metrics ? – Emna Jun 22 '18 at 9:03
1

Try out

https://docs.sonarqube.org/display/SONAR/Analyzing+Source+Code

Other possible ways

  1. If coding guidelines and standard followed.
  2. Duplicate code.
  3. Coding guidelines followed.
  4. Design principle effectiveness .
1

How about an code review from an experienced senior developer, so that you can focus more on practical tips.

Experience is incomparable to any tool at least in the current state of the tools.

Having said that, currently for JavaScript , we use linter tools for static code analysis which comes as plugins/extensions in all major IDEs.

  • You are right experience is necessary ; but why not jumping this experience into a tool – Emna Jun 22 '18 at 12:44
  • Ok , currently for JavaScript , we use linter tools for static code analysis which comes as plugins in all major IDEs. – Vishal Aggarwal Jun 25 '18 at 20:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.