3. Shortly about the project
Code quality when NOT using
Php Inspections (EA Extended)
Code quality when using
Php Inspections (EA Extended)
4. What we’ll be talking about
● about Static Code Analysis (SCA)
○ it’s about searching defects in software source code
● a little bit about Software Economics
○ introduction, change and ownership costs
○ which costs we can reduce with SCA
● Php Inspections (EA Extended)
○ what is it
○ what makes it special
5. Software economics
● introduction costs
○ initial project costs
○ fixed
● change costs
○ business value delivery costs
○ variable (also correlates with team velocity)
● ownership costs
○ automated testing
○ low (see also https://speakerdeck.com/theofidry/mutation-testing-phpdeveloperday)
7. Software economics: a place for SCA
● introduction costs
○ maybe, the most of solutions tend to build a convenience layer
● change costs
○ yes!
○ because SCA slows down software aging
● ownership costs
○ maybe, but there are better ways as e.g. mutation testing
8. Php Inspections (EA Extended)
● numbers:
○ 300+ rules
○ 12 rules groups
● key features:
○ runs on the fly (that’s why real-time)
○ supports automated issues fixers (quick fixes)
○ want to see in action?
● commercial support
○ Php Inspections (EA Ultimate)
9. Php Inspections (EA Extended): essentials
The most important rules groups are:
● Control-flow (20+ rules)
○ example follows
● Performance (20+ rules )
○ example follows
● Probable bugs (30+ rules)
○ example follows
For legacy projects please keep those groups enabled