Battle Ready Laravel: A guide to auditing, testing, fixing, and improving your Laravel applications

ContentsIntroductionSection 1: AuditingWhat's Covered?Planning Your Auditing StrategyGetting Into the Right MindsetRecording Your FindingsAutomated ToolingPHP InsightsEnlightnLarastanStyle CICode CoverageManual AuditingInvestigating "raw" Database QueriesFinding Incorrect AuthorisationChecking ValidationFinding "Fake Facades"Finding Business Logic in HelpersFinding N+1 QueriesFinding Controllers That Use Other ControllersFinding Logic and Queries in Blade ViewsFinding Hard-Coded CredentialsCheck Open Package RoutesReviewing Project DocumentationSection 2: TestingWhat's Covered?Planning Your Testing StrategyThe Benefits of Writing TestsSpotting Bugs EarlyMaking Future Work and Refactoring EasierChanging the Way You Approach Writing CodeTests-As-DocumentationProve That Bugs ExistStructuring Your TestsDirectory StructureChoosing What To TestTest StructureData ProvidersWriting the TestsPrioritising Mission-Critical Tests FirstWriting the Rest of the TestsBenefits of Writing the Easy Tests FirstPreventing Test FatigueTesting Your UI with Laravel DuskInstallationTesting a Simple FormDusk Pages and SelectorsRunning Failed Tests and GroupsCreating a CI Workflow Using GitHub ActionsUsing an .env.ci FileRunning the Test SuiteLarastanLaravel DuskOutputSection 3: FixingWhat's Covered?Planning Your Fixing StrategyUsing an Error Reporting SystemTypes of ErrorsThe Benefits of an Automated Error Reporting SystemError Reporting Using FlareUptime Checking, Queue Monitoring, and Scheduler MonitoringUptime Monitoring with Oh DearScheduler Monitoring with Oh DearQueue Monitoring with Oh DearUpdating PHP, Laravel, and PackagesUpgrading in Small IncrementsAutomating the Upgrade Using Laravel ShiftPlanning Upgrades EarlyUsing a Suitable Local Development EnvironmentUsing Tests to Fix BugsWhat is Test-Driven Development?The Advantages of Test-Driven DevelopmentThe Disadvantages of Test-Driven DevelopmentFixing a Real Bug Using Test-Driven DevelopmentSafely Removing Dead CodeChecking the Version Control HistoryScream TestLogging or Reporting the UsageRemoving the Code with an Atomic CommitSection 4: ImprovingWhat's Covered?Planning Your Improvement StrategyMaking the Most of PHP's Type SystemUsing Type Hints and Return TypesUnion TypesType Hints and Return Types in ClosuresDRYing Up Your CodeAdvantages of DRYing Up Your CodeWhen to DRY Up Your CodeRefactoring ConditionsReducing Indented CodeReplacing if and elseif with matchUsing the Nullsafe OperatorUsing Database TransactionsAdding the Database TransactionsManually Using Database TransactionsTips for Interacting with Third-Party ServicesUsing Automatic or Manual TransactionsDispatching Queued Jobs inside Database TransactionsImproving the Testability of Your CodeUsing Objects Over ArraysFinal WordsDiscount CodesFlareOh DearStyleCILaravel Security In Depth