Do you know how to manage errors with Code Auditor
Updated by Brady Stroud [SSW] 1 year ago. See history
123
<introEmbed body={<> Code auditing is an essential practice that empowers developers, quality assurance teams, and organizations to identify and rectify potential flaws, weaknesses, and security risks within their codebase. [SSW Code Auditor](https://codeauditor.com/) is the perfect tool to audit your code helping you find: - Broken links - HTML errors - Google Lighthouse issues </>} /> Every Sprint, some time should be devoted to resolving Code Auditor errors and warnings. To aid in this, long-lasting PBI items should be created and carried over each Sprint keeping a history of the work done. The PBI should contain a version number at the top which gets incremented by +1 every new Sprint following the ["Change x to y" rule](/change-from-x-to-y/). This is used to track how many Sprints the PBI has been active for. <figureEmbed figureEmbed={{ preset: "goodExample", figure: '<imageEmbed alt="Image" size="large" showBorder={false} figureEmbed={{ preset: "default", figure: \'PBI to track Code Auditor errors\', shouldDisplay: true }} src="/uploads/rules/managing-errors-with-code-auditor/screenshot-2023-06-12-at-07.45.16.png" />', shouldDisplay: true } } />
Categories
Related rules
Need help?
SSW Consulting has over 30 years of experience developing awesome software solutions.