The aim of testing is to reduce the risks occuring during software development, ranging from not working Software to the issues with deployment and installation. It means to find ALL bugs is very difficult and often economically unprofitable. But to bring them to an acceptable level is possible and necessary.If we want to develop our product in the future we must plan the testing.
In many companies, unfortunately, underestimate the influence of the static test on the quality of the final product. At first, let's start with terms to understand differences between static and dynamic testing. In contrast to dynamic testing, static testing finds causes of defects and help to prevent future failures. It often has a goal to educate team and new team members. Static testing is done before the dynamic test and accordingly, errors found at this stage costing us less.
Most people think that time spent in traffic jams or on long trips is kind of lost time, but now a lot of new things appeared to make use of that “waiting” time. For IT-specialists the most interesting and useful occupation will be podcasts. Let's see what podcasts are there on IT-topics, which may be interesting to professional audiences, both developers and managers, system administrators and the rest of IT-specialists.
Once, when I was working in one small company, I was offered to conduct an interview with a candidate for the QA engineer position. At that time I did not have experience in that, and naturally, the first thoughts were "What to ask? It is necessary to re-read urgently all the literature on testing! What to do?"