Recently the rise of unit testing, test-driven development, and agile methods has attested to a surge of interest in making the most of testing throughout all phases of the SDLC. However, testing is just one of many tools that you can use to ameliorate the code quality.
Almost every language has a tool that probe for violations of style guides, common gotchas, and sometimes crafty errors that can be hard to detect. Static analysis tool got in the reputation radar for giving a large number of false positive warnings and warnings to follow the style guide that are not necessarily required to follow.The good news about static analysis tools are that they can be configured to your needs. These tools can be configured either in your IDE or through command-line.
When rolling out a fresh new project, the team, unanimously should follow a certain standard of coding throughout the whole SDLC. In all, a coding standard should make it easier to work in the project, and maintain development speed from the beginning to the end.Obviosuly your linting tool will rain you with plethora of false positive error because it would not be able to guess your project`s coding pattern. But like I said earlier, they can be configured and you can roll your own static checker.
So, do not let testing be the terminal of your QA, make sure to take advantage of analysis tool.
No comments:
Post a Comment