This site uses cookies , both own and third parties , to collect statistical information about your browsing and show related advertising to your preferences , generated from your navigation patterns . If you go on surfing, we will consider you accepting its use.

Talks

Let’s extend the perception of static analysis methodology with other processes, beyond checking of the program source code. The idea of static analysis can be used not only for searching bugs, smells or incorrect formatting. Take a look at it in terms of fixing already existing knowledge of a team according to the resolved tasks. For example, you can keep records of the experience of preparing articles for publication, writing sections of the documentation, writing UI tests. By the way, there is a reason to talk about machine learning, which may reveal specific patterns.

The IT-market does not stand still and is actively evolving every day. If you want to release your software in a highly competitive market so that it has gained popularity, you cannot do it in a slipshod manner. That’s why before the release it is necessary to "catch" all bugs to avoid spending much time on negative reviews. It is far from certain that you will be given a second chance after a failure, even if you fix everything.

For this reason, an important task is the choice of quality control methods for your software. Test coverage is one of the popular methods of quality assurance. Properly organised testing gives good results, but is it enough? Static code analysis will be an excellent complement to testing. In this topic, we will talk about the basic aspects of static code analysis, ways of its integration into the development process and its advantages.