QA people traditionally focus on dynamic testing: they either click and type their way through the software under test as it executes, or they write automated tests that let the computer do that work for them. But does this approach overlook the potentially low-effort, high-reward approach of static testing? Static testing tools analyze the source code of the software under test without running it. At first glance, this might not look like a powerful or promising strategy, but static tools have come a long way since the glorified linters you might have tried years ago.
If you have questions such as:
- What kinds of problems can we find with static testing?
- Does static testing reduce the need for dynamic testing, or does it cover a different range of issues?
- How much time does it take to configure and run static testing tools?
- Are they easily integrated into CI/CD pipelines?
- Are their false-positive and false-negative rates acceptable?
- In short, can static testing improve the life of a QA professional, or is it yet another expensive technology of questionable value?
Come and find out the answers with Chris Cowell, one of #PNSQC2020’s award-winning speakers.